State of MCP servers
Census of the official MCP Registry, refreshed daily. Last refresh 2026-11-20.
The official MCP Registry lists 66,657 servers. 45,709 (69%) expose a remote endpoint. When we connected to every one of them, 26,049 completed the MCP handshake without sign-in, 13,916 answered but required OAuth or an API key, and 5,359 (12%) did not answer at all.
Key numbers
| Servers in the registry (latest versions) | 66,657 |
| Distinct publisher namespaces | 41,557 |
| With a remote endpoint | 45,709 |
| Local packages only | 20,261 |
| Remote: online, no sign-in | 26,049 (57%) |
| Remote: online, sign-in required | 13,916 (31%) |
| Remote: unreachable | 5,359 (12%) |
| Median handshake time (online) | 1,263 ms |
| Median tools per open server | 8 |
| Tools catalogued on open servers (first 80 per server) | 417,227 |
Transports
| streamable-http | 46,035 |
| sse | 1,152 |
Package registries
| npm | 17,312 |
| pypi | 5,397 |
| mcpb | 2,434 |
| oci | 1,983 |
| nuget | 183 |
What listed servers do
| Web Search & Scraping | 738 |
| Finance & Payments | 592 |
| Crypto & Web3 | 582 |
| Productivity & Docs | 567 |
| E-commerce & Shopping | 548 |
| Communication | 537 |
| Agents & Orchestration | 508 |
| Other | 441 |
| Cloud & DevOps | 340 |
| Analytics & BI | 300 |
| Image & Video | 292 |
| News & Content | 285 |
Bulk publishing
A handful of namespaces publish thousands of near-identical servers. The ten largest:
| io.github.sadri-dridi | 2,366 |
| io.github.mrfentmen | 2,099 |
| io.github.pipeworx-io | 1,936 |
| io.github.mcp-dir | 1,120 |
| io.usefulapi | 1,077 |
| io.github.CloudCorpRecords | 561 |
| io.github.theluckystrike | 424 |
| dev.cotlet | 398 |
| io.github.Evozim | 375 |
| ai.smithery | 213 |
This is why our index shows at most 20 servers per publisher.
Latest-version publish month
| 2026-04 | 1,520 |
| 2026-05 | 1,948 |
| 2026-06 | 2,296 |
| 2026-07 | 3,459 |
| 2026-08 | 5,517 |
| 2026-09 | 9,505 |
| 2026-10 | 16,587 |
| 2026-11 | 22,472 |
Method
We read every active latest version from registry.modelcontextprotocol.io, then send each remote endpoint an MCP initialize and tools/list request with a 12-second timeout. We never call tools. Details in the methodology.
Cite this
Agents Index, "State of MCP servers", 2026-11-20. https://agentsindex.org/reports/state-of-mcp/
Data is CC BY 4.0. Raw records: /api/agents.