What is the adoption and standardization status of Official MCP Registry?

Preview; API frozen at v0.1; "Registry API v1 GA: Ideating, no target date" — phase candidate, governed by MCP Registry Working Group. Adoption: unmeasured. Version: API v0.1 (frozen, preview). Last verified 2026-10-19.

How does Official MCP Registry compare to other discover protocols?

Official MCP Registry is one of 17 standards at step 1, Discover (What is here, and where?). It pairs with Model Context Protocol, MCP Server Cards (SEP-2127), Open Agentic Schema Framework, AI Catalog well-known file. It builds on Model Context Protocol. Every standard at this step is listed at https://agenticweb.wiki/category/discover/.

Official MCP Registry MCP Registry

1 · Discover

Official MCP Registry
Category	Discover
Governed by	MCP Registry Working Group
Status	Preview; API frozen at v0.1; "Registry API v1 GA: Ideating, no target date"
Phase	candidate
Implementation	developer trial
Adoption	unmeasured
Version	API v0.1 (frozen, preview)
Specification	https://modelcontextprotocol.io/community/working-groups/registry
Found at	GET /v0.1/servers
Last checked	2026-10-19
Freshness	current · checked 2026-10-19
Solves	Let agents discover my API or service, Expose tools to agents, Describe an agent's capabilities

Official MCP Registry is an agentic-web standard (endpoint) at step 1, Discover, governed by MCP Registry Working Group; its own status is "Preview; API frozen at v0.1; "Registry API v1 GA: Ideating, no target date"" (candidate). It answers: Where can an agent or client find a catalogue of public MCP servers, and how do sub-registries mirror it? Adoption is unmeasured, last verified 2026-10-19.

Discover The Official MCP Registry is the catalogue and API of public MCP servers run by the MCP Registry Working Group; sub-registries can mirror it ^[1]. Clients list servers with GET /v0.1/servers, and the registry's server.json schema is being aligned with the MCP Server Card ^[1].

Overview

The charter marks the registry as a preview with the API frozen at v0.1. It states Registry API v1 GA: Ideating, no target date, so no general-availability date exists ^[1]. The code lives in the modelcontextprotocol/registry repository ^[2].

The registry does not describe how an individual server behaves; that is the job of the Server Card and the MCP specification itself. This record was added on 2026-10-15 and has not yet been probed.

Discovery and probe

Registry API listing endpoint · GET /v0.1/servers

GET {registry_origin}/v0.1/servers
parse:     A JSON response listing MCP servers (server.json entries) indicates a registry implementing the v0.1 API
on absent: 404 or a non-JSON response means the origin does not host a v0.1 MCP Registry API

Not probed live: no-fixed-path. candidate record; probe rule pending

History

2026-10-15 — curated update 2026-10-15
2026-10-16 — use-case tags (auto)
2026-10-16 — version v1.8.1 (watcher)
2026-10-16 — version label restored to 'API v0.1 (frozen, preview)'; the repository tag v1.8.1 is the registry server software release, not the Registry API version, so the GitHub watch no longer drives version

Instances

No instances recorded yet.

References

The MCP Registry working group charter describes the official MCP Registry as in preview with its API frozen at v0.1 and lists 'Registry API v1 GA: Ideating, no target date'; the server listing endpoint is GET /v0.1/servers, and the server.json schema is being aligned with the Server Card (charter changelog entry 2026-07-30). — https://modelcontextprotocol.io/community/working-groups/registry (2026-07-30) VERIFIED
The registry source is published in the modelcontextprotocol/registry repository (checked 2026-10-15). — https://github.com/modelcontextprotocol/registry/ (2026-10-15) VERIFIED
v1.8.1 released 2026-08-06 — https://github.com/modelcontextprotocol/registry/releases/tag/v1.8.1 (2026-08-06) VERIFIED

JSON · Markdown