Skip to main content
The MCP Registry is currently in preview. Breaking changes or data resets may occur before general availability. If you encounter any issues, please report them on GitHub.
The MCP Registry is the official centralized metadata repository for publicly accessible MCP servers, backed by major trusted contributors to the MCP ecosystem such as Anthropic, GitHub, PulseMCP, and Microsoft. The MCP Registry provides:
  • A single place for server creators to publish metadata about their servers
  • Namespace management through DNS verification
  • A REST API for MCP clients and aggregators to discover available servers
  • Standardized installation and configuration information
Server metadata is stored in a standardized server.json format, which contains:
  • The server’s unique name (e.g., io.github.user/server-name)
  • Where to locate the server (e.g., npm package name, remote server URL)
  • Execution instructions (e.g., command-line args, env vars)
  • Other discovery data (e.g., description, server capabilities)

​
The MCP Registry Ecosystem

The MCP Registry is part of an ecosystem that looks something like: The MCP Registry ecosystem

​
Relationship with Package Registries

Package registries — such as npm, PyPI, and Docker Hub — host packages with code and binaries. The MCP Registry hosts metadata that points to those packages. For example, a weather-mcp package could be hosted on npm, and metadata in the MCP Registry could map the “weather v1.2.0” server to npm:weather-mcp.