MCP Registry
The official centralized metadata repository for publicly accessible MCP servers. Use it for discovery, but treat preview status and server trust as separate concerns.
What It Is
The MCP Registry is the official catalog and API for discovering Model Context Protocol servers. It provides a common metadata layer so clients, IDEs, hosted agents, and internal platforms can find MCP servers programmatically instead of scraping README lists.
Official status as of 2026-06-18: the registry is still preview. The docs warn that breaking changes or data resets may happen before general availability. Source: MCP Registry docs, https://modelcontextprotocol.io/registry/about, 2026-06-18
What It Provides
- canonical metadata for public MCP servers
- API-first discovery surface
- open-source registry implementation
- ecosystem-backed metadata repository
- path for clients to browse/install capability providers
The registry is backed by major MCP ecosystem contributors including Anthropic, GitHub, PulseMCP, and Microsoft. Source: MCP Registry docs, 2026-06-18
What It Does Not Provide
The registry is not a trust oracle. A registered MCP server can still be unsafe, verbose, poorly scoped, or low quality. Security, permissions, auth, output limits, and tool design remain the responsibility of the client/operator.
Do not equate "discoverable" with "approved." For Kevin's stack, registry discovery should flow through Agent Capability Registry, Capability Routing Map, Golf - MCP Agent Security, and project-level tool permissions.
Routing
Use the MCP Registry when:
- a harness is MCP-first
- the task needs a tool/data source that is not already installed
- a client needs to discover server metadata programmatically
- evaluating whether a capability already exists before building one
Prefer an agent-native CLI when:
- the workflow is repeated by a shell agent
- local cache/SQL/compound domain commands matter
- token budget is tight
- the service has a strong first-party CLI
Relationship to Ecosystem Marketplaces
The official registry is the protocol-level metadata layer. Third-party directories and marketplaces can add hosting, reviews, analytics, OAuth, ratings, enterprise controls, or curated bundles on top. Keep those layers distinct in docs: registry = discoverability, marketplace = packaging/curation, governance = local approval.
Timeline
- 2026-06-18 | Updated preview status from official registry docs and clarified discovery vs trust/governance. Source: MCP Registry docs, https://modelcontextprotocol.io/registry/about, 2026-06-18
- 2026-06-18 | Cross-linked Agent Capability Registry as the broader local layer above public MCP metadata. Source: whole-wiki graph audit, 2026-06-18
- 2025-09-08 | Official MCP Registry launched in preview at
registry.modelcontextprotocol.ioas an open catalog plus OpenAPI spec with sub-registry support. Source: MCP Blog, https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/, 2025-09-08 - 2026-05-31 | Tool page created from the registry repo and preview announcement. Source: modelcontextprotocol/registry, https://github.com/modelcontextprotocol/registry, 2026-05-31