Open reliability data for MCP servers

GET https://faceabot.com/api/reliability-feed.json            JSON, 1,000 servers per page, follow "next"
GET https://faceabot.com/api/reliability-feed.csv             same data as CSV
GET https://faceabot.com/api/reliability-feed.json?verdict=reliable   only proven-reliable servers
GET https://faceabot.com/api/reliability?url=https://example.com/mcp   one server

id (official MCP Registry name) · url · verdict · attempts · successes · successRate · consecutiveSuccesses · lastStatus · lastCheckedAt · lastLatencyMs · toolsAdvertised · work (real read-only task: verdict proven_working / partly_working / not_working / testing / not_tested, tool, attempts, successes, sampleInput) · page · badge

Verdicts: reliable ≥ 95 % success over ≥ 3 checks and ≥ 3 in a row · measuring fewer than 3 checks · flaky 60–95 % · failing < 60 % · requires_authentication private server, not a failure.

Reuse, mix and display freely, including commercially. Please show this credit next to the data:

<a href="https://faceabot.com">Reliability data: Faceabot</a>

Or embed the live badge of any server: <img src="https://faceabot.com/badge/<id>.svg">

Each check is an MCP initialize then tools/list; when the server declares a read-only tool (readOnlyHint), Faceabot also calls that one tool with a neutral sample input (e.g. https://example.com, hello world) to check it really returns a result — never a tool that writes, sends, pays or deletes. Everything is sent politely (one request per host at a time, backoff on errors) with the User-Agent FaceabotProbe/1.0 (+https://faceabot.com/reliability; opt-out: https://faceabot.com/api/reliability/opt-out). Server owners can opt out at /api/reliability/opt-out. Publishers can diagnose their own server with the Faceabot doctor.