Goodword's MCP connection was ready for the Claude directory review queue.
The connection had already been tested directly. A person could add Goodword to Claude, search their professional network, view relationship context, and continue working without leaving the conversation.
A directory entry was a different part of the product. It needed to explain the connection to somebody who had not received setup instructions from the Goodword team.
The submission required a name, description, service endpoint, authentication flow, and a clear account of the tools made available after installation. The words had to describe actual actions rather than a broad promise about what an assistant might eventually do.
Installation also needed a safe failure state. If a person had not connected an account or authorization had expired, the tool should ask them to reconnect instead of returning an empty result that looked like a real answer.
The directory description emphasized that the source was the user's own Goodword relationship data. A search through that connection was different from a public internet search and should remain visibly attributed to the authorized account.
This was a submission, not an acceptance. Goodword had moved from a connection shared through manual setup to one packaged for review in a broader MCP directory.
The work followed the March tests inside Claude. Those tests established that the search path could return a useful relationship result. The May submission required the same path to be understandable to a new person starting from a directory page.
The entry went into the review queue. Acceptance, placement, and later changes remained separate events.