Independent Report on MCP Server Reliability and Security Findings
The first independent security and reliability report on MCP servers has been published, analyzing data from 2,181 remote MCP server endpoints. The report covers reliability, security, and maintenance metrics gathered through monitoring of publicly accessible endpoints.
Key Findings from the Analysis
- 52% of remote MCP server endpoints are dead
- 300 servers have zero authentication, meaning any agent can connect
- 51% have wide-open CORS (Cross-Origin Resource Sharing) configurations
- The finance category scores lowest on trust despite handling sensitive data
- Only 42% of servers with GitHub repositories have committed code in the last 30 days
Available Resources
The full report with detailed methodology is available at yellowmcp.com/report. Developers can test their own MCP servers using the tool at yellowmcp.com/test.
📖 Read the full source: r/ClaudeAI
👀 See Also
OpenClaw User Adds TOTP 2FA After Agent Exposed API Keys in Plain Text
An OpenClaw user created a security skill called 'Secure Reveal' that requires TOTP authentication via Telegram before displaying stored credentials, after their AI agent accidentally leaked API keys and passwords in plain text during a demo.
Tool Authority Injection in LLM Agents: When Tool Output Overrides System Intent
A researcher demonstrates 'Tool Authority Injection' in a local LLM agent lab, showing how trusted tool output can be elevated to policy-level authority, silently changing agent behavior while sandbox and file access remain secure.
Security Benchmark: 10 LLMs Tested Against 211 Adversarial Probes
A security researcher tested 10 LLMs against 211 adversarial attacks, finding that extraction resistance averages 85% while injection resistance averages only 46.2%. Every model failed completely on delimiter, distractor, and style injection attacks.
Sandboxing AI Agents with WebAssembly: Zero Authority by Default
Cosmonic argues that traditional sandboxing (seccomp, bubblewrap) fails for AI agents due to ambient authority. WebAssembly's capability-based model grants zero authority by default, requiring explicit imports for filesystem, network, or credentials.