Everybody building with MCP wants to know the same thing: how many servers are out there? The answer depends on what you count and where you look. We did the work. Here is what the MCP ecosystem actually looks like in late May 2026 — by the numbers, across every major source.
The Short Answer
Somewhere between 6,000 and 55,000, depending on how you define “exist.”
That range is not a cop-out. It reflects a real split between servers that are maintained and documented versus listings that were published once and never updated. The number you care about depends on what you are trying to do.
Breaking Down the Count
Public Registries
The largest public directories give you the broadest view of raw supply:
- MCP.so lists over 19,000 server entries. This is a community-submitted directory with no formal review process. Anyone can add a listing by opening a GitHub issue. Volume is high, but signal-to-noise is low.
- MCP Market catalogs more than 10,000 servers across 23 categories. Community-curated with a browsable web interface, but no programmatic API and no verification layer.
- Smithery hosts over 7,000 servers with both local CLI install and hosted remote options. Closer to a package manager than a directory — you can actually run servers directly from Smithery’s infrastructure.
- Official MCP Registry (registry.modelcontextprotocol.io) is a metaregistry backed by Anthropic, GitHub, PulseMCP, and Microsoft. It stores metadata only — no code, no binaries. The canonical upstream source for other registries to index against.
Add in GitHub repositories tagged with MCP, npm packages, PyPI distributions, and Docker images, and the raw listing count crosses 50,000. But raw listings are not the right metric.
What “Production-Ready” Looks Like
Most of that long tail is unmaintained. Many listings are forks of the same base server with minor modifications. Others are tutorial projects, proof-of-concept demos, or abandoned experiments from late 2025 when MCP was new and everyone wanted to build a server.
A more useful number: roughly 1,300 to 2,000 servers are in active production use across enterprises and developer workflows as of mid-2026. That estimate comes from cross-referencing registry download counts, GitHub commit activity, and install command usage patterns.
The Curated Layer
At AgentNDX, we take a different approach. Every server in the directory is hand-reviewed for documentation quality, install reliability, and real-world usability. The current count:
- 405 curated MCP servers across 10 categories
- 166 verified with confirmed working installs and documented auth
- 324 with active health status (responding and maintained)
- 93 agent skills tracked in the skills directory
That is less than 1% of the raw total. It is also the slice that actually works when you need to ship something.
Where the Servers Are: Category Breakdown
Not all categories grew equally. Here is how 405 curated servers break down:
| Category | Count | Share |
|---|---|---|
| Data | 106 | 26% |
| Productivity | 62 | 15% |
| Infrastructure | 61 | 15% |
| AI | 36 | 9% |
| Code | 29 | 7% |
| Communication | 25 | 6% |
| Web | 25 | 6% |
| Media | 23 | 6% |
| Payments | 22 | 5% |
| Identity | 17 | 4% |
Data dominates. Database connectors, vector search, ETL pipelines, and enrichment APIs make up more than a quarter of the usable server base. This tracks with how agents are actually used — most agentic workflows involve reading from or writing to structured data sources.
Payments and identity are small but growing fast. These categories barely existed in early 2026. The emergence of x402 payment-gated servers and OAuth-based identity layers signals that MCP is maturing beyond read-only tooling into transactional capabilities.
Transport and Auth Patterns
How servers connect tells you as much as what they do:
- 82% use stdio transport — the original MCP transport, where the client spawns the server as a local subprocess. Still dominant because it is simple and works everywhere.
- 18% use HTTP transport — remote servers accessible over the network. Growing as more teams deploy MCP servers to cloud infrastructure rather than running them locally.
- Less than 1% use SSE — server-sent events transport is effectively legacy at this point, superseded by streamable HTTP.
On the auth side:
- 72% require an API key — the most common pattern, usually from the underlying service the server wraps
- 17% use OAuth — more common in enterprise and productivity integrations
- 11% require no auth — typically local-only servers or open data sources
- Less than 1% use x402 — payment-gated access is live but early
What the Numbers Tell You
Three takeaways from this census:
1. Discovery is the bottleneck, not supply. There are enough MCP servers for almost any use case a developer or agent might need. The hard part is finding the right one among thousands of options — and knowing whether it actually works. Curated registries matter more than exhaustive ones.
2. stdio and API keys won. At least for now. Despite early predictions that remote HTTP servers would quickly overtake local installs, 82% of production servers still run locally via stdio. The simplicity tax of remote deployment (auth, hosting, latency) has slowed adoption. That will shift as more managed MCP hosting services launch, but stdio is not going away.
3. The long tail is real and mostly noise. Over 90% of MCP server listings across public registries show no commit activity in the past 60 days. For developers evaluating servers, recency of the last update is a stronger signal than star count or listing position.
FAQ
Q: How does the MCP server count compare to REST API directories? A: ProgrammableWeb tracked over 24,000 REST APIs at its peak. The MCP ecosystem crossed that number in under 18 months — though with more fragmentation and less standardization. The difference is that MCP servers are designed to be consumed by AI agents directly, not through human-written integration code.
Q: Which MCP registry should I use to find servers? A: For breadth, start with MCP.so or Smithery. For curated, production-ready recommendations, use AgentNDX. For enterprise governance with access control and audit logging, consider the Official MCP Registry combined with an internal gateway.
Q: Are there more MCP servers than anyone can actually use? A: Yes. Supply outpaced demand starting in late 2025. The market is consolidating now — quality over quantity. Expect the number of actively maintained servers to plateau while the raw listing count keeps climbing.