MCP Registry
The official MCP Registry is the public index of published MCP servers. Its read API is unauthenticated and exposes server metadata, version history, package entries, remote endpoints, repository links, website links, lifecycle status, and update timestamps.
Data Model
- Server names use reverse-DNS form with one slash, such as io.github.owner/server or com.example/server.
- Versions are immutable server.json snapshots. latest resolves to the current version for a server name.
- Packages describe installable distributions such as npm, PyPI, NuGet, or OCI images plus transport details.
- Remotes describe hosted MCP endpoints and their transport type.
- Official metadata carries status, published time, update time, and whether the row is latest.
Workflows
- Find servers — Search by server name substring, then inspect titles, descriptions, status, deployment types, and links.
- Inspect one server — Fetch latest or a specific version before comparing packages, remotes, repository, and website metadata.
- Track changes — Use RFC3339 updated_since filters for incremental registry monitoring; deleted rows can appear when incremental sync includes them.
- Audit a namespace — Filter returned rows by namespace prefix such as com.mcpbundles/ to see publication coverage, statuses, and deployment surfaces.
- Plan downstream ingestion — Prefer latest active rows with remotes when building a hosted-server directory; package-only rows can still matter for local stdio install flows.
Gotchas
- Search is simple: the registry search parameter is a case-insensitive substring match on server names, not semantic search over descriptions.
- Path encoding: server names contain /; detail and version requests must URL-encode the full server name.
- Preview service: the registry is in preview and does not guarantee uptime or data durability. Treat it as a source to sync periodically, not as the only runtime data store.
- Deleted status: deleted rows are hidden by default and mainly appear when explicitly requested or when using incremental sync.
