Diagrams · Fig. 14

Where the numbers come from

The server count is a defined population, not a scrape. Every stage carries its exclusion rule.

Where the numbers come fromThe registry population funnel. All entries from the official MCP registry are narrowed by excluding delisted and superseded versions, leaving the active latest-version entries that mcpindex publishes as its server count. A reachability probe narrows that to the reachable remote servers that form the drift-ledger population. Quality scoring and a semantic index produce the ranked searchable corpus behind the servers, search and leaderboard pages. A screen queue that takes adversarial cases first produces the advisory screen verdicts, which are REVIEW or UNVERIFIED at v1.registry.modelcontextprotocol.iothe canonical upstreamexclude delisted + superseded versionsactive latest-version entries18,574the number we publishreachability probereachable remote serversthe drift-ledger populationquality scoring + semantic indexranked + searchable corpus29categories/servers · /search · /leaderboardscreen queue, adversarial cases firstadvisory screen verdictsREVIEW / UNVERIFIED at v1DELISTED AND SUPERSEDED VERSIONS ARE EXCLUDED SO THE SAME SERVER NEVER COUNTS TWICE. A DEFINED POPULATION, NOT A SCRAPE.
Fig. 14 · The server count is a defined population, not a scrape. Every stage carries its exclusion rule.
Read Fig. 14 as text
  registry.modelcontextprotocol.io          all entries
        |  exclude delisted + superseded versions
        v
  active latest-version entries             18,574 servers  <- the number we publish
        |  reachability probe                29 categories
        v
  reachable remote servers                  the drift-ledger population
        |  quality scoring (lib/quality.ts) + semantic index
        v
  ranked + searchable corpus                /servers - /search - /leaderboard
        |  screen queue (adversarial cases first)
        v
  advisory screen verdicts                  REVIEW / UNVERIFIED at v1

  delisted and superseded versions are excluded so the same server never
  counts twice. the count is a defined population, not a scrape.
What the figure says

The registry population funnel. All entries from the official MCP registry are narrowed by excluding delisted and superseded versions, leaving the active latest-version entries that mcpindex publishes as its server count. A reachability probe narrows that to the reachable remote servers that form the drift-ledger population. Quality scoring and a semantic index produce the ranked searchable corpus behind the servers, search and leaderboard pages. A screen queue that takes adversarial cases first produces the advisory screen verdicts, which are REVIEW or UNVERIFIED at v1.

Where this is explained
/stats
Use this diagram

Licensed CC BY 4.0. Use it anywhere, including commercially. Keep the credit.

Credit line (HTML)

Paste under the figure. That is the whole licence obligation.

<a href="https://mcpindex.ai/diagrams/corpus-pipeline">Where the numbers come from - mcpindex.ai</a> (CC BY 4.0)
Direct SVG

Standalone image/svg+xml. Vector, editable, no stylesheet needed.

https://mcpindex.ai/diagrams/corpus-pipeline/svg

Last reviewed 2026-07-27 · derived live from getServerCount, getCategoryCount · never hand-typed

Questions this answers

how many mcp servers are there &middot; mcp registry size &middot; mcp server count &middot; mcp directory methodology