MCP Station Report: Registry Changes and Reachability, November 2, 2026

Reachability

On the checked day, 2026-11-01, MCP Station’s index held 35,902 servers. All 35,902 were checked, and 31,662 were reachable, a share of 88 percent. For anyone connecting to a remote MCP server, this means roughly one in eight listed entries did not answer at the time of the check. A client or agent that relies on a listing should expect some endpoints to fail and should handle timeouts and missing servers.

Reachability also shifted over the period 2026-10-31 to 2026-11-01. 128 servers came back, and 123 went down. The two numbers are close, so the overall level looks fairly steady. Underneath, though, a similar number of servers moved in each direction. A server that worked yesterday may not work today.

Listings and schema changes

In the same period, 1,592 servers were newly listed. 557 servers changed their schema, and these changes covered 2,143 tools. A schema change can alter the name, description or parameters of a tool. Agents that cache tool definitions, or that have been prompted to use a tool in a certain way, may then send calls that no longer fit.

Tools added and removed

369 servers added tools, for a total of 1,364 new tools. 101 servers removed tools, for a total of 522 removed tools. Added tools widen what an agent can do and also what it has to consider when choosing a tool. Removed tools can break workflows that depend on them, and the failure may only show up when the tool is called.

New destructive tools

47 servers introduced new tools that are marked as destructive, 162 tools in all. Destructive tools are those that can delete or overwrite data or cause other changes that are hard to undo. For people who connect agents to servers, new tools of this kind are a reason to review permissions and approval settings. Many clients ask for confirmation before such calls, and a change in a server’s tool list may justify checking that these settings still match the intended use.

These figures are measurements from one two-day window. They describe what changed and do not assess any individual server.

Measured changes

31,662 of 35,902 remote MCP servers answered on the 2026-11-01 check.

Largest categories

About this data

Measurements by MCP Station, which checks every remote server in the Official MCP Registry daily. Measurements are not a security guarantee and are not an endorsement of any server. Methods: mcpstation.net/methods.html. Data: mcpstation.net/api.

Disclosure: the operator of Emerge Times also operates MCP Station.

This article was prepared with AI assistance and reviewed by an Emerge Times editor before publication. Licensed CC BY 4.0: credit “Emerge Times (emergetimes.com)”. Usage & License