MCP server health, State of MCP census
TrustBench
io.github.lithvall/trustbench
x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).
- remote_404
Checks
The exact rows akashi check io.github.lithvall/trustbench prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | pass | pushed 0d ago |
| package npm | pass | published (1.1.1) |
| remote reachable | fail | 404 (endpoint gone) |
| at least one live entrypoint | pass | 2 alive |
| license present | warn | none detected |
Evidence
Packages
- npm @trustbench/mcp · published(1.1.1)
Remote endpoints
- https://trustbench.io/mcp
streamable-http · not_found· HTTP 404
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check io.github.lithvall/trustbenchInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check io.github.lithvall/trustbench --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.