Agent MCP Directory

Official MCP Registry vs GitHub MCP Registry

Product engineer: Publish to the official registry first; it is the source others read. Developer-platform lead: Treat GitHub's list as curated reach inside VS Code and Copilot, not as the registry of record. Agent builder: Query the official API for breadth and GitHub's for a short list with repo metadata.

The sourced difference

The official registry holds 56,677 latest entries published by anyone who proves a namespace; GitHub's registry lists 773 servers, 587 with a remote, with GitHub metadata such as stars and licence. (Official MCP Registry: Official MCP Registry API, GET /v0/servers, counted on 4 November 2026 and modelcontextprotocol/registry on GitHub, read 5 November 2026; GitHub MCP Registry: GitHub MCP Registry API, GET /v0/servers, counted on 4 November 2026 and GitHub MCP Registry API, GET /v0/servers, observed on 4 November 2026)

Verdicts by reader

Official MCP Registry or GitHub MCP Registry, by who is asking
ReaderVerdict
Product engineerPublish to the official registry first; it is the source others read.
Developer-platform leadTreat GitHub's list as curated reach inside VS Code and Copilot, not as the registry of record.
Agent builderQuery the official API for breadth and GitHub's for a short list with repo metadata.

Side by side on the rubric

Official MCP Registry and GitHub MCP Registry on the same rubric
DimensionOfficial MCP RegistryGitHub MCP Registry
Remote transportrecords bothrecords remotes
OAuth with client registrationnot applicablenot applicable
Per-tool auth scopingnot applicablenot applicable
Hosting and scale limitsnot a hostnot a host
Observabilitynot applicableCopilot usage metrics count MCP servers
Pricingfreefree
Registry submissionCLI with namespace verificationnot documented on the page
Discoverability by agentsopen paginated APIopen API and install buttons
Own server in the registriesnot applicableyes

Evidence for every cell is on the profiles: Official MCP Registry and GitHub MCP Registry.