TL;DR: MCP server quality still lags adoption, according to Arcade, because agents act on tool metadata rather than human review. MCP deployment needs stronger semantics, safety notes, failure guidance, and credential handling before it can be treated as production ready.
Editorial analysis by NHI Mgmt Group, based on content published by Arcade: “What Scanning 90,000 MCP Servers & 630,000 Tools Reveals About Agent-Ready Tools”.
By the numbers:
- Only 260 of the open-source servers we scored earn an A, and none earn an A+.
- Stateless handling appears on 5.8% of servers, and those servers average about eight points higher.
Key questions
Q: Why do stateless MCP servers require tighter authorization than session-based designs?
A: Stateless handling removes reliance on a prior handshake or session ID, so each request has to stand on its own.
Q: What are the signs that an MCP deployment is being used unsafely by agents or downstream users?
A: Warning signs include unknown fields being accepted, risky write operations proceeding without approval, repeated retries creating duplicate actions, and tool calls reaching unexpected hosts or regions.
Q: What breaks when an MCP server's tool descriptions do not match its actual actions?
A: The trust model breaks.
Practitioner guidance
- Define tool semantics as governance artefacts Document what each tool changes, what it returns, when it should be used, and when it should not.
- Annotate destructive and irreversible actions Mark reset, delete, and other state-changing tools with explicit safety annotations and require user confirmation before execution proceeds.
- Remove credentials from tool parameters Pass secrets through controlled identity channels instead of embedding them in prompts or inputs where they can be logged or replayed.
Bottom line: MCP server quality is now an identity and governance issue because agents act on tool metadata, not just on human review.
Glossary terms: MCP Server, Tool Annotation, Stateless protocol, Destructive tool
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP tool definitions have become a governance boundary, not a developer convenience. When an agent chooses between tools at runtime, the metadata attached to those tools is effectively part of the authorization surface. Missing descriptions, weak schemas, and unclear failure handling do not just reduce usability; they change how authority is exercised inside the workflow. Practitioners should treat server quality as a control issue, because the agent can only remain bounded if the tool contract is explicit.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: Should teams prioritise safety annotations or richer tool documentation first?
A: Safety annotations come first when tools can delete, reset, or otherwise change state irreversibly. Rich documentation still matters, but a clear warning about consequence is the minimum control for high-risk actions. In practice, teams should fix both, then validate that the agent can distinguish safe reads from destructive calls before the server is approved for production.
👉 Read our full editorial: ToolBench shows MCP quality still lags enterprise adoption