deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Serverdex scan of 21,700 MCP servers finds 10% dead and a median 4,800-token context cost

A daily probe of ~21,700 remote MCP servers found roughly one in ten unreachable, over a quarter demanding credentials, and tool definitions that can exceed an entire 200K context window.

Serverdex scan of 21,700 MCP servers finds 10% dead and a median 4,800-token context cost

A long-running measurement of the MCP ecosystem suggests public tool servers are in better shape than the widely repeated claim that most listed servers are abandoned — but a meaningful slice of directory listings is genuinely lifeless. According to an analysis by Serverdex published on dev.to, roughly one in ten of the ~21,700 remote MCP servers it probed was unreachable or answered with something other than the MCP protocol. The figures come from a scan on 21 November 2026.

Serverdex probes every listed MCP server that exposes a remote endpoint roughly once a day using a credential-free initialize call followed by a tools/list request, then records what comes back. In the November scan, 64% of remote servers completed the handshake without any sign-in, 26% answered but only after a required sign-in such as an OAuth flow or an API key, and 10% were unreachable or not speaking MCP. Directories, the analysis notes, rarely distinguish between these outcomes: a server published a year ago and down for months still shows up as an installable listing.

Credentials are the first thing to vet

Of the servers that answered, about 28% demanded credentials before exposing a single tool. Serverdex frames this as unremarkable in itself — authentication and deployment servers legitimately need keys — but as the cheapest and most useful first check when deciding what to connect an agent to.

The analysis also reports scanning roughly 310,000 tool definitions for hidden instructions embedded in descriptions and finding the problem effectively nonexistent. Its argument is that the real exposure with an MCP server is capability: a powerful tool attached to an agent without anyone reviewing what it can actually do.

Tool definitions eat context on every turn

Every connected server's tool definitions are loaded into the model's context before the user's prompt is read, and the measured distribution is highly uneven. The median answering server exposes 14 tools and loads about 4,800 tokens of definitions. The heaviest tenth load around 41,000 tokens, and the single largest server measured loads about 247,000 tokens — more than an entire 200K-token context window from one connection, before the agent has done anything.

Protocol versions signal maintenance

About 78% of answering servers implement the current 2025-06-18 revision of the MCP specification, with the remainder on older versions. Serverdex treats a server frozen on a year-old protocol revision as a maintenance warning, on the theory that it usually means nobody is looking after it.

Method and limitations

A server counts as answering when it completes the handshake, with or without a required sign-in; the failure category covers both unreachable servers and those replying outside the protocol. Token figures are estimated by dividing the character count of the raw tool definitions by four, so they measure what a client sends rather than runtime behaviour. Servers distributed only as local packages — npm or PyPI installs with no hosted endpoint — cannot be probed from outside and are therefore excluded from the liveness numbers. The published figures are a snapshot; Serverdex says its live version updates hourly.

Why it matters

Anyone wiring agents to third-party tool servers is currently choosing from catalogues that assert liveness without testing it. A ten percent failure rate means a non-trivial share of integration effort goes to endpoints that will never respond, and the checklist the numbers imply — does it answer, does it want your keys, how much context do its tools consume, and can you read what they do — costs minutes to run and prevents both dead ends and silent context bloat. For maintainers, the message is that a reachable endpoint, a readable tool list and honest scoping are now the practical standard by which their server will be judged.

  • #mcp
  • #ai-agents
  • #llm
  • #developer-tools
  • #context-window

Related posts