The reliability index

How to read this

• This is not uptime. It is the share of our checks that succeeded. A failed check can be their outage, our runner, or the network — only the first is a fact about the project, and we only started recording which was which on 2026-09-01.
• An MCP handshake is strong evidence; an HTTP reach is weak. A parked domain answers HEAD. A tools/list response cannot be faked by a parked domain.
• “Answers a call” is a stronger fact than “answers a handshake”. Each MCP server is asked one read-only call a day, picked from its own tool list: a list_/get_/search_ name carrying no mutating verb anywhere in it (get_swap_quote is refused despite the prefix), taking no required arguments and declaring none that look like an address, a key or an amount. A dash means we did not ask — never that the server failed, and errored is not a verdict either: one common answer is a server telling us an argument it did not mark as required is in fact required, which is the server working.
• Before 2026-09-01 a bot-block (HTTP 403) counted as a failure. Records spanning that date mix two definitions. Rows whose failures are all unattributable are shown but ranked last, marked not established.
• ✓ install verified means the documented install and entry were reproduced in an ephemeral container by us, on the date shown. It says nothing about runtime safety.