State of the MCP registry
October 2026. The official MCP registry lists 38,992 servers. We read every entry and checked the ones that run as remote endpoints. Here is what we found.
11% of remote servers fail the MCP handshake
Of 22,587 remote endpoints we checked on 2026-10-04, 14,029 (62%) completed the MCP handshake, 6,007 (27%) asked for sign-in first, 63 asked for payment, and 2,488 did not complete it: no response, an HTTP error, or a reply that is not valid MCP. Failures for a network reason were checked again.
3,463 linked repositories no longer resolve
3,463 of the 23,013 GitHub repositories linked from registry entries (15%) return “not found”: deleted, renamed away or made private. Another 247 are archived.
4 publishers account for 15% of all entries
io.github.sadri-dridi (2,365), io.github.pipeworx-io (1,716), io.github.mcp-dir (1,113), io.github.mrfentmen (802). Together 5,996 of 38,992 entries. We keep their pages but do not ask search engines to index them one by one.
744 entries read like tests
Names such as -test, -demo or -ok. They are listed, flagged, and ranked lower.
16% of answering servers speak protocol 2026-07-28
Among the 14,029 servers that completed the handshake, the protocol revision they settled on: 2025-11-25 5,471 · 2025-03-26 4,390 · 2026-07-28 2,217 · 2025-06-18 1,487 · 2024-11-05 464.
The median server lists 8 tools; 287 list more than 50
Across 12,091 servers that returned a tool list: median 8, 90th percentile 31, largest 1,376. Every tool definition takes room in an agent's context.
What these numbers do not say
A server that answers the handshake is up; that does not make it safe or correct. Servers that run locally (npm, PyPI, Docker) cannot be checked from outside and are not in the percentages. A failed check is a snapshot: a server can be down for an hour.
Method · Data (CSV, CC BY 4.0) · Cite: doi:10.5281/zenodo.23137127 · Registry read 2026-10-03, GitHub read 2026-10-04, endpoints checked 2026-10-04.