The real state of live MCP servers: 9 in 10 answer, and what they cost you
Originally published on Serverdex , where these numbers update live. Every large MCP directory shows you a server count. Almost none of them tell you whether those servers are actually alive . A listing is a claim. A server that was published a year ago and has been down for months still sits in most catalogues with a green card and an install button. What you actually need to know before you…
According to live data from Serverdex, 90% of remote MCP servers actually respond to handshakes. Of the approximately 21,700 servers measured, 64% answered with no sign-in required, while 26% responded after a required sign-in such as OAuth or an API key. About 10% were unreachable or replied with something other than the MCP protocol.
However, the data reveals that nearly a quarter of the servers that responded required authentication credentials before exposing any tools. While this is not inherently concerning, it's an important factor to consider before connecting to a server. Only 9 in 10 remote servers were found to be alive and functional, highlighting the need for live liveness checks rather than relying solely on directory listings.
Each connected server's tool definitions are loaded into the model's context before reading your prompt, which incurs a significant cost. The median server requires about 4,800 tokens worth of definitions, while the top 10% load up to 41,000 tokens per connection, potentially exceeding a full 200K context window. This context tax varies greatly among servers, with some loading as much as 247,000 tokens.
Furthermore, 78% of the responding servers adhere to the current MCP protocol (2025-06-18), while the remaining 22% are running older revisions. Servers stuck on outdated protocols are often neglected and may indicate poor maintenance.
Before connecting to an MCP server, four key questions should be addressed: Does it answer? Does it require credentials? What does it cost your context? Can you read its tools? By asking these questions, you can make informed decisions about which servers to connect to, ensuring a secure and efficient use of MCP servers.
Rewritten by urgent.news; may contain errors — check the original.
Source: dev.to