What MCP Registry does
MCP Registry is a hosted metadata repository for publicly available MCP servers, with a REST API that MCP clients and aggregators query to discover them. Server creators publish a single server.json entry giving the server's unique name, where to locate it and how to execute it, and the registry stores that metadata pointing at package registries such as npm, PyPI and Docker Hub rather than hosting the code itself.
Why teams reach for it: It is the canonical record the rest of the ecosystem reads from - a server creator publishes once and MCP clients, aggregators and marketplaces all reference the same data - and the registry adds no ranking, curation or quality judgement of its own, leaving that to the subregistries that ETL from it.
How MCP Registry compares
Fields the vendor doesn't document are left blank here rather than guessed — a blank means nothing verified, not a "no."
- Public Api
- Yes
- Submission Model
- Verified ownership required
How will people and clients find it?
Registries & discovery tools are directories or catalogs that help people and AI clients find MCP servers that already exist.