MCP server statistics

The same two series, per source

The official registry is the spine of this catalogue and everything else is supplementary. Each record is counted once, under the source that established its identity, so the four figures below add up to the catalogue rather than overlapping. The three charts that follow keep their own scale: the registry is two orders of magnitude larger than Docker's catalogue, and a shared axis would flatten the smaller two into nothing.

Official MCP registry, 28,298 servers

Servers whose identity comes from the official MCP registry. This is the only source with a publish date and an update date for every entry, so it is the only one of the three whose curve means much on its own.

Smithery, 1,297 servers

Servers this catalogue holds because Smithery lists them and the registry does not. Smithery publishes tool schemas at scale, which is why it is worth joining, but its pagination caps at 500 records per query, so this is a sample of its index rather than all of it. The shape of this series says as much about our crawl as about Smithery.

Docker MCP catalogue, 156 servers

Servers this catalogue holds because Docker's MCP catalogue lists them and the registry does not. That catalogue is curated rather than open to submissions, and small, so single months of 1 or 2 are normal here and a flat month is not a stall.

When we first listed each server

Every record also carries the date this catalogue first held it, which is a different fact again from either date above. It is published here because it is the honest series for the question "what did this site add", and because it must not be mistaken for the registry's own history. It measures our collection schedule: the first month holds the entire catalogue as it stood when the field was introduced, and later months hold whatever a run picked up.

So a reader wanting the ecosystem should use the first published series, and a reader wanting to know what is new on this site should use this one. They will not agree, and neither is a correction of the other.

How to read these numbers

A spike can be one publisher rather than growth

The registry does not limit how many entries one publisher may create, and several have registered large batches in a single day. That lands on this page as a tall bar, which reads as the ecosystem accelerating when it is one namespace filling in. The table below names the largest publisher namespace in every month where one namespace accounted for at least 10 percent of the registry entries first published that month, so a bar can be checked instead of trusted. Servers that reached this catalogue through Smithery or Docker are left out of these figures, because they carry no registry namespace to group by.

The largest single case is August 2026, where 1,004 of the 8,174 registry entries first published that month share the namespace io.github.mcp-dir. Naming it states what the registry record says and nothing further: a publisher is entitled to register as many entries as it wants to, and we make no claim about what any of them do.

Published is not written, and it is not released

The first published date is the moment the registry accepted an entry. Plenty of MCP servers existed for months before their publisher got round to registering one, and a few registered an entry before there was much to install. Treat the series as the registry's intake, which is what it is, rather than as the date the software appeared.

There is no honest count of versions published per month

The registry's primary key is a name and a version, so counting versions per month needs one row per version. The dump we hold does carry per version dates, and that is exactly why we checked it rather than assumed: it holds 9,095 version rows across 3,503 servers, of which 1,228 have more than one version, and its newest version date is 3 August 2026. That is a fraction of the 29,756 servers here, and the crawl behind it stopped part way through the alphabet, between ac.inference.sh/inference and com.stagenth/memory-kit. A monthly series drawn from it would collapse after 3 August 2026 for reasons that have nothing to do with the registry, so we do not draw one, and the second chart on this page is labelled last updated rather than updates.

What that dump does support is published here rather than thrown away, with its limits in the caption. Read it as the shape of version activity among 3,503 servers whose names sort before com.stagenth/memory-kit, and not as a catalogue wide figure.

The newest month is always incomplete

This page was generated on 8 September 2026, so September 2026 holds only the part of the month that had happened by then. Nothing is projected forward to fill it. The rolling 3 month figure quoted at the top and on the home page has the same edge, and says so in both places.

Checking any of this

Every figure here is counted from the JSON records in this catalogue and written to one file before the page is built, so the page states numbers rather than working them out. If one of them is wrong, the aggregate is wrong and it is rebuilt by a single command. Corrections are welcome, and a publisher correcting their own entry in the registry fixes it here on the next pass.