MCP CENSUS
stats · a98c22ad-41af-43d4-b43d-2121779b7368

MCP server statistics

How many Model Context Protocol (MCP) servers exist, how fast the official registry grows, and how many have problems. Each finding below is one sentence you can quote, with a link and its method. The numbers refresh daily.

Current daily projection · source 2026-11-02T14:44:08.208Z · generated 2026-11-02T14:44:05.062Z

Findings

  1. As of 2 November 2026, The MCP Census tracks 56,952 MCP server records. #

    Method: Count of server records in the census database. Most come from the official MCP Registry; the rest come from other public sources. One record per server name.

  2. The 56,952 MCP server records in The MCP Census come from 25,106 distinct publishers. #

    Method: Distinct publishers in the census publisher index.

  3. The official MCP Registry listed 55,070 unique servers on 2 November 2026, up 42% from 38,893 on 3 October 2026. #

    Method: Unique server names in the census's daily walk of the full official MCP Registry. The earlier point is the newest daily walk at least 30 days before the latest.

  4. The official MCP Registry grew from 15,494 unique servers on 8 July 2026 to 55,070 on 2 November 2026, 3.6 times as many. #

    Method: Same daily registry walk. 8 July 2026 is the first day the census recorded.

  5. As of 2 November 2026, 14% of MCP servers in the census (8,087 of 56,952) have at least one verified problem, such as a deleted or archived repository or a deprecated package. #

    Method: Health verdict "issues": one or more fact-based problem flags. See the health verdict in the methodology.

  6. As of 2 November 2026, 72% of MCP servers in the census (41,212) have no verified problem under current rules. #

    Method: Health verdict "healthy": no verified problem flags. This is not a security or code-quality claim.

  7. 7,653 MCP servers in the census (13%) do not yet have enough evidence for a health verdict, and the census leaves them unknown instead of guessing. #

    Method: Health verdict "unknown" plus records not yet assessed.

  8. As of 2 November 2026, 65% of MCP servers in the census (36,941) declare a hosted remote endpoint instead of only a local install. #

    Method: Records with at least one remote URL in their registry entry.

  9. In the census's latest live MCP probes, 22,848 hosted MCP endpoints answered and 879 did not; 13,447 have not been probed yet. #

    Method: Live probe: server/discover (2026-07-28 revision) with an initialize fallback. An OAuth challenge counts as alive. Probe counts are per endpoint observation, so they need not add up to the hosted-endpoint count.

  10. 42% of MCP servers in the census (23,852) publish under a DNS-verified namespace and 57% (32,581) under a GitHub-verified namespace. #

    Method: Namespace kind from the official MCP Registry: domain namespaces are DNS-ownership-verified, io.github namespaces are GitHub-verified. Never inferred from the name alone.

  11. Of 24,473 MCP endpoints whose protocol era is known, 4,874 (20%) speak the modern 2026-07-28 protocol and 19,599 still use the older initialize handshake. #

    Method: The census asks each endpoint which revision it speaks and reports the answer. Endpoints not yet asked, or gated by OAuth, are excluded from this sample.

  12. Of the MCP servers in the census, 2,805 appear in the Awesome MCP Servers list, 13,054 on Glama and 493 on Smithery. #

    Method: Citation checks against each public directory, matched to census records.

Questions

How many MCP servers are there?

As of 2 November 2026, The MCP Census tracks 56,952 MCP server records. The official MCP Registry listed 55,070 unique servers on 2 November 2026, up 42% from 38,893 on 3 October 2026.

How fast is the MCP Registry growing?

The official MCP Registry listed 55,070 unique servers on 2 November 2026, up 42% from 38,893 on 3 October 2026. The official MCP Registry grew from 15,494 unique servers on 8 July 2026 to 55,070 on 2 November 2026, 3.6 times as many.

What share of MCP servers have problems?

As of 2 November 2026, 14% of MCP servers in the census (8,087 of 56,952) have at least one verified problem, such as a deleted or archived repository or a deprecated package. 7,653 MCP servers in the census (13%) do not yet have enough evidence for a health verdict, and the census leaves them unknown instead of guessing.

How many MCP servers are remote?

As of 2 November 2026, 65% of MCP servers in the census (36,941) declare a hosted remote endpoint instead of only a local install. In the census's latest live MCP probes, 22,848 hosted MCP endpoints answered and 879 did not; 13,447 have not been probed yet.

How to cite

Quote the sentence and link its anchor. Suggested credit:

The MCP Census, “MCP server statistics”, 2 November 2026, https://mcpcensus.com/stats

The page keeps this URL and these anchors; the numbers change daily, so please include the date.

Sample, method and limits

All counts share one daily projection of 56,952 server records. Registry growth comes from the census's daily walk of the official MCP Registry. A missing fact stays unknown and is never estimated.

These are public observations. They do not certify code, permissions, scopes, runtime isolation or security. Full rules: methodology.

Raw counts: coverage · machine-readable: /v1/coverage · July 2026 deep analysis: report.

Check one server

Look up any MCP server by name, namespace or repository on Lookup, or check a whole agent config before you install it with Preflight.