API TRACKER RESEARCH · BY APIDECK
A dated view of the Official MCP Registry. Ten findings you can inspect, reproduce and cite.
Snapshot: · One registry · Frozen edition
TRANSPORT METADATA
Share of all 53,075 records. Multiple transports can appear on one record, so these shares overlap.
Every count below refers to the same frozen snapshot. Each heading has a permanent citation link.
API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 53,075 distinct registry names.
This is a count of registry identities, not unique products, active deployments or users.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 70 records classified as official by API Tracker out of 53,075 registry records.
This measures our evidence-review coverage, not the share of the ecosystem that is official.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 53,004 records with unverified publisher affiliation out of 53,075 registry records.
Unverified does not mean unofficial, unsafe or unsupported.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 1 record classified as community-maintained out of 53,075 registry records.
This classification is evidence-based; it is not inferred from the absence of an official badge.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 35,571 records with a recorded remote endpoint URL out of 53,075 registry records.
A URL does not establish availability, authentication requirements or browser compatibility.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 35,342 records with a repository URL out of 53,075 registry records.
A repository link does not establish a license, source availability or maintenance activity.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 33,150 records with a website URL out of 53,075 registry records.
A missing website field does not mean the project has no website.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 35,192 records listing Streamable HTTP out of 53,075 registry records.
Transport values are recorded metadata, not results of connection tests.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 20,836 records listing stdio out of 53,075 registry records.
A record may list multiple transports. Transport counts overlap.
Source & methodology ↗API Tracker’s 2026-11-01 snapshot of the Official MCP Registry contains 1,119 records listing SSE out of 53,075 registry records.
This is the snapshot’s SSE label; it does not establish protocol-version compatibility.
Source & methodology ↗Source: Official MCP Registry. We credit its maintainers and contributing publishers. MCP Connect produced the catalog snapshot; API Tracker by the Apideck team calculated this report. Glama, Smithery and PulseMCP are not included in this edition.
Authentication adoption, registry overlap, active deployments and growth are not measured. This single snapshot cannot distinguish new projects from newly indexed records. No claim is made that it covers every available MCP server.
Download aggregate report & SHA-256 hashes · Reproduction script · Directory methodology
API Tracker by Apideck. “MCP statistics: November 2026 registry snapshot.” Observed November 1, 2026. Specify the statistic and link to its heading so readers can inspect its scope.
https://apitracker.io/mcp-statistics/2026-11-01This edition is frozen. Corrections should be disclosed; future observations get their own dated editions. Our monthly review process requires a complete source snapshot and human review before publication.
Suggest a correction →