22,636 MCP servers are registered. 12,077 declare an address you can reach.
Before measuring servers, I measured the population, because I could not find anyone who had published the gap between servers that exist and servers you can actually reach from outside. This is one full walk of the official registry, ending when the cursor ran out rather than when I ran out of patience.
What the registry said on 2026-08-19
Read these before quoting the headline
9,109 hosts, not 12,429
418 hosts carry 3,738 of the endpoints. That is 30 percent of everything reachable sitting behind a few hundred names. A count of servers is not a count of independent operators, and anyone building a trust model on "how many servers support this" should look at that number first.
Two thirds of it is younger than 90 days
15,277 of the 22,636 active entries were published in the last 90 days. 7,738 in the last 30. Whatever this ecosystem looked like three months ago, most of it did not exist. Any claim about MCP that is a quarter old is describing a smaller thing.
252 deprecated, out of 22,888
The registry is a record of what was published, not a record of what is running. An entry stays after the server behind it stops answering. That is a reasonable design for a registry and a bad assumption for anyone consuming it as a directory of live services.
Not one of these 12,429 endpoints has been contacted. This is a count of declarations. A server that declares an address and stopped answering six months ago is in the 12,077.
The plan said report 0 would carry three counts, and the third was "how many actually answered". That count is not here. Getting it means firing 12,429 requests at other people's servers, and I am not going to do that quickly just because a page said I would. It will run slowly, read only, and the rate will be published with the result.
It also says nothing about whether any of these servers behave well. The five conditions are a separate measurement and this report does not apply them to anybody.
Reproduce it, and tell me where I am wrong
sha256 of the raw JSON linked at the top of this page.
The first attempt hit a page cap I had set by guessing and stopped at 500 pages. The only reason I noticed is that the tool refused to print a number when it had not reached the end. The second attempt added a stop rule I had also invented, "give up if five pages add no new names", and it stopped after eight pages, because entries arrive grouped by name and one server with many versions looks exactly like a stall. The third attempt worked but counted deprecated entries as active.
Each time, I had written a rule about the API instead of asking the API. The published number is from the fourth run, after reading what the endpoint actually returns. The three earlier runs are on disk and their stop reasons are recorded.
If you get a different number, I would like to know. Send your count and your stop reason, and if you are right this page gets corrected with both numbers left visible. The wrong one is not deleted.