The MCP Registry acts as an app store for Model Context Protocol (MCP) servers, allowing MCP clients to discover and access a list of available servers. It has reached an API freeze for v0.1, ensuring stability for integrators while continuous development is ongoing for future versions.

Is registry open source?

Yes, licensed under NOASSERTION.

registry: The MCP Registry acts as an app store for Model Context Protocol (MCP)… (★ 7k, NOASSERTION)

Features

01Provides server discovery for MCP clients, acting as an app store for MCP servers.

02Ensures API stability with a v0.1 freeze, allowing integrators to confidently implement support.

03Supports multiple authentication methods for server publishing, including GitHub OAuth/OIDC and DNS/HTTP verification.

04Validates namespace ownership for published entries to maintain integrity and trust.

05Offers a comprehensive local development environment easily launched with `make dev-compose`.

Why choose it

+Provides server discovery for MCP clients, acting as an app store for MCP servers.

+MCP clients discovering and connecting to available MCP servers.

+Covers 6 supported environments or platforms, which is helpful for broader deployment needs.

+Ships with a public repository and a NOASSERTION license, which makes adoption and review easier.

Trade-offs

!There are at least 8 related tools in the same category, so the best choice is easier to make after side-by-side comparison.

Compatibility

Model Context Protocol (MCP) clients

Native Support

Verified via docs

Model Context Protocol (MCP) servers

Native Support

Verified via docs

GitHub OAuth

Supported Auth

Verified via docs

GitHub OIDC

Supported Auth

Verified via docs

Docker

Container Support

Verified via docs

PostgreSQL

Database Support

Verified via docs

Quick start

$ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest

Use cases

↳MCP clients discovering and connecting to available MCP servers.

↳MCP server developers publishing and making their servers discoverable.

↳Integrators building applications that leverage the MCP Registry API for server management.

How it compares

≈registry sits in the RAG / Knowledge Base category, so it makes more sense to evaluate it alongside tools like mindsdb instead of in isolation.

≈If your main need is closer to "MCP clients discovering and connecting to available MCP servers.", that use case is a better lens for comparison than broad feature checklists alone.

≈registry uses a NOASSERTION license, and community traction are both easier to judge in category context.