AI Potluck
Contribute
Back to Gap Map Product / UX / Agent protocols & SDKs

Official MCP Registry

Model Context Protocol project
open source / Overall score: 2.0

The Model Context Protocol's own catalogue of MCP servers - an API and a hosted service that lists what servers exist and how to reach them, with a publishing flow for server authors. Run by the protocol's maintainers rather than a vendor.

GitHub's classifier reports NOASSERTION because the LICENSE opens with a licensing transition notice before the Apache text; the body is the same file the specification repository carries.

Openness

5 high confidence
5.0
license
Apache-2.0(OSI
source
public(the registry service and its API)
core features withheld
no — the hosted instance runs the published code

The LICENSE is the protocol's own transition file: Apache-2.0 for new code, MIT retained for contributions whose authors did not consent to relicensing, and CC-BY-4.0 for documentation other than the specification. The documentation licence is recorded separately because it does not govern the artifact you run.

  • https://api.github.com/repos/modelcontextprotocol/registry recorded 2026-09-17

    Repository metadata: 7,258 stars, not archived, last pushed 2026-09-16, description "A community driven registry service for Model Context Protocol (MCP) servers."

  • https://raw.githubusercontent.com/modelcontextprotocol/registry/main/LICENSE recorded 2026-09-17

    The LICENSE body, read rather than the classifier's label: it opens "The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0" and then carries the Apache terms, with MIT retained for pre-transition contributions. That transition preamble is what GitHub's classifier cannot match, and it is why the API reports NOASSERTION.

Adoption

2 low confidence
2.0

The registry is a hosted service with no published request or listing count and no package to install, so GitHub stars are the only countable signal, but a star is not a use. That understates the product: what matters about a registry is how many clients read it, and nobody publishes that figure.

Capability

not assessed

No score is given here, and for a different reason than the specifications above: a registry implements no part of the client-server contract — no role, no primitive, no transport. It is the protocol's discovery service, listing servers rather than speaking to them, and it has an entry here because it is infrastructure the protocol itself defines and governs.

Verified 2026-09-17