MCP registry
An MCP registry is a public directory of Model Context Protocol servers that agents and developers search to find an MCP surface for a given service. Registries include the official community-run MCP Registry at registry.modelcontextprotocol.io and third-party directories such as Smithery. A registry listing is a discovery signal: it makes an API's MCP server findable by name instead of by prior knowledge.
Registries are the search layer of the MCP ecosystem. A manifest at a well-known path answers "does this domain have a server?"; a registry answers the reverse question — "who has a server for this service?" — which is the question an agent or developer usually starts with. Entries typically carry the server's name, description, and connection details, so a match resolves directly into a usable integration.
For producers the listing is low-effort and compounding: it is metadata, not infrastructure, and once published it makes the MCP server reachable from every tool that queries the registry. An unlisted server still works for anyone who already knows its address; it simply forfeits the path by which new integrators find it.
Discry's registry discovery check runs a deterministic probe of a public MCP registry (Smithery) for the API's registrable name and passes when a listed server matches it. The matched name ships in the check detail, so the result is reproducible.
Checks: MCP registry · how each is scored
What does an AI agent make of your API?
Find out in about a minute — no signup.
Discry your API — free