Official MCP Registry (MCP Registry Working Group): The community metaregistry of MCP servers under the modelcontextprotocol project, published to with the mcp-publisher CLI after namespace verification; the pack calls it the Anthropic MCP registry. Remote transport: records both. Price read 4 November 2026: Free to publish and read (read 2026-11-04).
Fact sheet
Product
Official MCP Registry (registry.modelcontextprotocol.io)
Does not verify that a listed endpoint works or what its tools do.
Does not rank or grade servers.
Is still a preview; data resets are possible.
Dated facts
The registry launched in preview on 8 Sep 2025 and its API entered a v0.1 freeze on 24 Oct 2025; v1 is planned for GA. (github.com, dated 8 September 2025, read 4 November 2026)
Publishing uses the mcp-publisher CLI, not a pull request; adding a server.json to the repo does not list a server. (github.com, read 4 November 2026)
Namespaces are verified by GitHub OAuth, GitHub OIDC from Actions, DNS or HTTP; io.github.<user>/ needs that GitHub login and reverse-DNS names need domain proof. (github.com, read 4 November 2026)
A full GET of /v0/servers with version=latest on 4 Nov 2026 returned 56,677 entries: 55,806 active and 871 deprecated. (registry.modelcontextprotocol.io, read 4 November 2026)
37,977 of those entries declare at least one remote: 37,751 streamable-http remotes and 1,127 sse remotes. (registry.modelcontextprotocol.io, read 4 November 2026)
Entries carry the 2025-12-11 server.json schema, with remotes, packages, websiteUrl and repository fields. (registry.modelcontextprotocol.io, read 4 November 2026)
The registry does not grade servers; status is limited to active or deprecated in the official _meta block. (registry.modelcontextprotocol.io, read 4 November 2026)