The network indexes 3,042 MCP servers across 3,018 providers at apis.io/servers/. Roughly one server per provider — which tells you most of what you need to know about where Model Context Protocol adoption currently sits.
Against a catalog of more than 25,000 providers, 3,018 is 12%.
What the ratio says
One server per provider is the signature of a first implementation. A provider with a mature MCP posture would ship several — a read-only server for safe queries, a scoped write server, perhaps one per product line, mirroring how they already decompose their REST surface.
Nearly everyone has shipped exactly one. That is the “we should have an MCP server” phase, not the “MCP is how agents consume our platform” phase.
Compare with the same providers’ REST surfaces from this week’s profiles: Adyen decomposes 202 APIs into 20 named collections; Slack splits 115 across 32. Nobody is decomposing their agent surface that way yet.
The gap this sits inside
The completeness scan behind this week’s rebuild puts numbers on it. Across published providers, the missing-surface counts are:
- MCP — 22,420 providers without one
- Agent Skills — 23,071 without
- Arazzo workflows — 24,863 without
- Spectral rules — 21,858 without
MCP is, by that measure, the most adopted of the agent-facing artifacts. It is still absent from seven providers in eight.
Why the largest providers are missing
The deepening targets from the same scan are pointed. Amazon Web Services — 1,804 APIs, the largest surface on the network — has no MCP server, no Arazzo, no agent skills. Microsoft Graph (564 APIs) is missing MCP, Arazzo, and skills. GitHub (384) has no MCP. Datadog (290) is missing MCP and skills.
These are not companies without engineering capacity. They are companies whose API surfaces are large enough that “expose this to agents” is a genuine design problem rather than a weekend project. Wrapping 1,804 AWS APIs in an MCP server raises immediate questions about scoping, cost, and blast radius that a 10-API startup never faces.
Which is exactly why the YC portfolio covered today reads more agent-native than a growth-stage book: less surface to reconcile.
What to do with the index
The index is browsable by provider, and it is most useful as a negative filter. If you are choosing between two providers for an agent-facing integration, the one with a described MCP server is the one your agent can adopt without you writing an adapter. Today that filter eliminates 88% of the catalog.
Takeaway
3,042 servers, 3,018 providers, 12% of the catalog, and almost exactly one server each. MCP adoption is real and it is shallow — a first implementation nearly everywhere, a considered agent surface almost nowhere, and absent entirely from the largest API platforms on the network.
Browse the index at apis.io/servers/.