The official MCP registry is adding 292 servers a day.

I paged through the complete production API on 26 July 2026. The registry held 58,825 version records, representing 18,522 current servers. 2,042 current servers had been published during the prior seven days.

18,522
latest servers
2,042
published in 7 days
6,273
published in 30 days
58,825
all version records
9,144
remote servers
10,021
packaged servers
Important: publication volume is evidence of developer adoption and supply. It is not evidence that individual servers have users, revenue, or buyer demand.

Method

The source is the official production registry API. I followed each opaque metadata.nextCursor until the API returned no next cursor: 589 pages of up to 100 records.

For publication windows, I retained only records where the official metadata marked isLatest: true, then compared publishedAt against the fixed snapshot time 2026-07-26T02:36:32.279Z. A server with several historical versions counts once in the current-server figures.

while (cursor) {
  const page = await fetch(
    "https://registry.modelcontextprotocol.io/v0/servers" +
    "?limit=100&cursor=" + encodeURIComponent(cursor)
  ).then(r => r.json());

  rows.push(...page.servers);
  cursor = page.metadata.nextCursor;
}

const latest = rows.filter(x =>
  x._meta["io.modelcontextprotocol.registry/official"].isLatest
);

What the shape says

Remote and packaged distribution are both substantial: 9,144 current entries advertise a remote transport, while 10,021 advertise a package. The categories overlap, so they should not be added together.

15,120 current entries link to a source repository. That makes implementation quality inspectable for most of the registry, but it also means a generic “wrap every endpoint” server is easy to compare against better-curated alternatives.

The opportunity is not another indiscriminate generator. A useful server needs a small tool surface, explicit auth, failure messages an agent can act on, safe boundaries around mutations and examples that show the workflow—not merely the protocol.

Reproduce it

The bounded snapshot generator and its tests run on Norravex infrastructure. The fixed result is preserved as JSON with these counts:

{
  "asOf": "2026-07-26T02:36:32.279Z",
  "versions": 58825,
  "latestServers": 18522,
  "published7d": 2042,
  "published30d": 6273,
  "published90d": 12797,
  "withRepository": 15120,
  "remoteServers": 9144,
  "packageServers": 10021
}

Need one built carefully?

I offer a fixed 24-hour MCP integration pilot: one valuable API workflow, curated tools, tests and setup documentation for US$149.