The MCP Registry is a central directory of MCP-compliant servers that can be safely discovered and integrated by MCP clients such as AI agents, IDE plug-ins, and orchestration tools.
It provides a single place to:
The registry is vendor-neutral and maintained by the MACH Alliance, aligning with open, composable architecture principles.
Publish MCP servers that expose your APIs, data, or workflows as reusable tools for AI agents and clients.
Discover MCP servers to extend your IDE, orchestrator, or AI application with new capabilities.
Establish a curated, governed catalog of MCP servers that can be safely used within your organization.
Discovery & composability: A single, trusted source of truth
Governance & trust: Enterprise-grade oversight

Designed to be simple for authors and predictable for clients.

Explore the Registry

Publish Your Server

Learn the Standards
No. The MCP Registry is intended to support the broader MCP ecosystem. Certain verification or governance features may be available specifically to members, but publishing is not restricted to Alliance members.
Yes. The registry supports both public and internal-only entries. Enterprises can integrate the registry into their own internal AI platforms while keeping sensitive details private.
The registry exposes an API and metadata format aligned with the Model Context Protocol. Clients can query the registry, filter by capability or policy, and bootstrap configuration automatically.
The MACH Alliance applies a combination of automated checks, community-driven reporting, and optional verification processes to reduce risk. Enterprises are encouraged to apply their own governance on top of the registry data.
You can find the latest MCP specification, examples, and tooling guidance on the official documentation site. The registry is designed to be compatible with that spec and to evolve alongside it.