# MCP server health receipts

MCP health receipts are the liveness record of the MCP servers listed on a2ally: a background probe re-checks each listed server on a fixed cadence (at most three servers per pass, stalest first), and every probe is published as one append-only, hash-chained receipt — the time, the outcome, the latency, the tool count and the tool-definition fingerprint the server answered with. An outcome is a probe fact: up means the server's MCP handshake (initialize + tools/list) answered from this deployment at that time; down means it did not answer; redirected means the registered URL now redirects elsewhere, so the answer was not recorded as this server's; changed means it answered with tool definitions whose fingerprint differs from the recorded one. None of these is a finding that a server or its tools are safe. State transitions are also sealed into the public ledger as change observations; the full receipt history lives on this surface.

Probes run on the deployment's cadence, not on read: reading this surface never probes a server. A server with no receipts yet has not been probed since this record began — that is stated as an empty history, never filled in or back-dated.

## Listed servers

No MCP servers are listed yet.

Machine form: https://www.a2ally.com/v1/mcp-health · one server: https://www.a2ally.com/v1/mcp-health/{slug} · the listed servers themselves: https://www.a2ally.com/v1/store/external