What is the MCP Registry?

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:

  • Register & describe your MCP server
  • Discover new capabilities for your MCP client
  • Apply governance & trust policies
  • Standardize metadata across vendors

The registry is vendor-neutral and maintained by the MACH Alliance, aligning with open, composable architecture principles.

Who is this for?

MCP server authorsDevelopers & product teams

Publish MCP servers that expose your APIs, data, or workflows as reusable tools for AI agents and clients.

  • Increase discoverability for your server
  • Provide clear capabilities & limits
  • Signal compatibility & support status
MCP client buildersTooling & platform engineers

Discover MCP servers to extend your IDE, orchestrator, or AI application with new capabilities.

  • Search by capability, domain, or vendor
  • Filter by maturity, license, or verification
  • Automate client configuration from registry data
EnterprisesArchitects, security & governance teams

Establish a curated, governed catalog of MCP servers that can be safely used within your organization.

  • Align MCP usage with internal policies
  • Track ownership & support contacts
  • Enable approved MCP clients to consume trusted servers

Benefits for the MCP ecosystem

Discovery & composability: A single, trusted source of truth

  • Instead of hard-coding server definitions into each client, use the registry as a single, evolvable source of truth for MCP servers.
  • Reduce configuration drift
  • Promote reuse across teams & tools
  • Accelerate experimentation with new capabilities

Governance & trust: Enterprise-grade oversight

  • Apply governance without blocking innovation. Use the registry to maintain a curated list of servers that align with your policies.
  • Optional verification & review signals
  • Clear ownership and support metadata
  • Separation of public vs. internal entries
Start publishing
Benefits for the MCP ecosystem

How does it work?

Designed to be simple for authors and predictable for clients.

  • Submit server metadata: Provide a minimal, standardized description of your MCP server: endpoints, capabilities, auth model, and support details.
  • Validation & governance: The registry validates schema compatibility and applies any required governance rules or moderation checks.
  • Discover & integrate: MCP clients and orchestration tools can query the registry to discover servers and bootstrap configuration automatically.

Get Involved:

Annual research

Explore the Registry

Hero MCP Registry

Publish Your Server

Explore the Registry

Learn the Standards

FAQ:

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.