The State of MCP Reliability
April 2026
The first independent assessment of reliability, security, and maintenance across the MCP server ecosystem
Executive Summary
Key Findings
35% of remote MCP endpoints are dead. Out of 2,181 remote-capable servers, 761 fail to respond — timeout, connection refused, or not found.
218 servers (10.0%) have zero authentication. Any agent can connect and execute tools without credentials.
50% have open CORS (Access-Control-Allow-Origin: *), allowing cross-origin requests from any domain.
Finance scores lowest on trust despite handling the most sensitive data — a notable gap between risk and security posture.
Ecosystem Overview
YellowMCP indexes 20,348 MCP servers from the Official MCP Registry, Smithery, PulseMCP, mcpmonitoring.com, and community lists. Of these, 2,181 have remote endpoints that can be independently monitored.
Data Sources
Category Distribution
Reliability Assessment
Server Status (2,181 remote endpoints)
30-Day Uptime Distribution
Latency Distribution
Top 10 Most Reliable Servers
| # | Server | Category | Uptime | Latency | Trust |
|---|---|---|---|---|---|
| 1 | Netdata★79,437 | dev-tools | 99.7% | 583ms | 100 |
| 2 | ContextLattice★121 | productivity | 100.0% | 401ms | 95 |
| 3 | edgar.tools SEC Intelligence★2,413 | dev-tools | 100.0% | 540ms | 95 |
| 4 | PostHog MCP Server★35,203 | dev-tools | 100.0% | 506ms | 100 |
| 5 | AWS Knowledge★9,331 | dev-tools | 100.0% | 409ms | 100 |
| 6 | ChromaDB Remote MCP Server★12 | dev-tools | 100.0% | 386ms | 100 |
| 7 | MCP Registry Server★6,966 | dev-tools | 99.0% | 632ms | 100 |
| 8 | io.github.tldraw/tldraw★48,399 | dev-tools | 98.6% | 1069ms | 95 |
| 9 | ShipSwift★2,323 | dev-tools | 99.7% | 563ms | 95 |
| 10 | ai.smithery/truss44-mcp-crypto-price★39 | finance | 99.8% | 763ms | 95 |
Security Intelligence
2,180 remote MCP servers scanned with 5 passive security checks: authentication, transport security, CORS policy, information leakage, and SSL/TLS certificate quality.
Trust Score Distribution
218 servers have zero authentication
10.0% of remote MCP servers respond with 2xx and no authentication required. Any agent can connect and execute tools without credentials. This is the #1 security concern in the ecosystem.
Authentication
SSL/TLS Certificates
Trust Score by Category
Maintenance & Activity
Of 1,206 remote servers with linked GitHub repositories, only 0% have committed code in the last 30 days. Abandoned MCP servers represent a growing reliability risk — they accumulate security vulnerabilities and drift from protocol updates.
Methodology
Health Monitoring
Every remote endpoint is checked via HTTP GET/SSE handshake every 5-15 minutes. We record status code, response latency, and error details. Servers are classified as up (2xx within 10s), degraded (slow or intermittent), reachable (401/403), or down (timeout/error).
Security Scanning
All checks are passive and non-intrusive. We assess authentication requirements, transport security (HTTPS), CORS headers, information leakage (server headers, error details), and SSL certificate validity. No penetration testing or active exploitation.
Trust Score
Starts at 100. Deductions: no authentication (-30), HTTP only (-25), invalid SSL (-20), expiring SSL (-10), weak auth (-10), error details exposed (-10), open CORS (-5), server headers exposed (-5), low uptime (-10 to -30). Range: 0-100.
Limitations
Uptime data reflects only the monitoring period (since April 1, 2026). Servers without remote endpoints cannot be health-checked. Security scans assess external posture only — internal architecture and code quality are not evaluated. Trust scores are not endorsements.
Recommendations
For developers choosing MCP servers
Check uptime history before depending on a server. Verify it requires authentication. Look at GitHub commit activity — a server with no commits in 90 days is a maintenance risk. Use YellowMCP's agent discovery tools to find reliable servers at runtime.
For MCP server operators
Claim your listing on YellowMCP to verify ownership. Add authentication — 13.8% of the ecosystem is wide open. Monitor your uptime and set up alerts. Embed a reliability badge in your README to signal quality.
For the ecosystem
The MCP ecosystem has a quality layer problem. Registries list servers but don't verify they work. Discovery tools don't assess security. The gap between “listed” and “production-ready” is where reliability intelligence fits.
Share this report
Stay updated on MCP reliability
Get the monthly State of MCP Reliability report and ecosystem insights.
No spam. Unsubscribe anytime.