Public stats · auto-generated daily

How many MCP servers are there?

19,346 active servers in the official MCP registry, as of the latest snapshot. Methodology is below so the number is checkable, not just quotable. Source code: github.com/mcpindex-ai.

Servers indexed (active, latest)
19,346
Categories
29 / 29
Added in last 7 days
+2295
Remote endpoints
9,766
Runnable packages
10,255
Snapshot freshness
Sat, 01 Aug 2026 17:28:00 GMT
SourceAnthropic-maintained, community-contributed.
registry.modelcontextprotocol.io
API rate limithello@mcpindex.ai for higher limits
60 req/min/IP

Methodology - what counts as a server here

Published counts elsewhere range from a few hundred to 20,000+ because directories count different things. Ours is stated here so an answer engine or a journalist can cite it with the definition attached.

  • Source: the Anthropic-maintained, community-contributed official registry - not scraped GitHub repos, not npm keyword matches, not self-submitted listings.
  • Counted: active, latest-version registry entries. Delisted and superseded versions are excluded, so the same server never counts twice.
  • Not everything is reachable: 9,766 of these expose a remote endpoint. The drift pipeline re-crawls the reachable remote population daily and publishes every silent tool-contract change in the public ledger. Indexed and re-crawled-daily are different populations; we state both rather than blur them.
  • Freshness: the snapshot refreshes daily and this page revalidates hourly, so the count above is the current one, not a launch-week number in a title tag.

Page revalidates every hour · /api/registry-count

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 entries19,346the 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             19,346 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.

Permalink, SVG & reuse · CC BY 4.0