mcpbeat

TrustBench MCP Server

io.github.lithvall/trustbench
answering

TrustBench is answering right now. Last checked 5 min ago. 37 installs a week from npm. It exposes 3 tools. Last commit 4 Aug 2026.

x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).

Installs per day peak 15 · avg 4 · +16% w/w
a month agotoday
Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
327 ms
Response time
average over 24h
37
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add trustbench --transport http https://trustbench.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "trustbench": {
      "url": "https://trustbench.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.trustbench]
url = "https://trustbench.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trustbench": {
      "url": "https://trustbench.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "trustbench": {
      "url": "https://trustbench.io/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rankings
get_rankings
Get TrustBench liveness rankings for x402 providers by capability. Returns a scored list of providers with latency and success-rate telemetry. Methodology note: scores are derived from HEAD-probe liveness checks (3 samples from one host), not a rigorous benchmark. See trustbench.io/methodology. Output: returns a JSON array. Each object has name (string, provider name), score (number 0-100, composite liveness score), latency_p50 (number, ms), success_rate (number 0.0-1.0, last 7 days), endpoint (string, URL), capabilities (array of strings).
receipt
get_receipt
Fetch a TrustBench routing receipt by ID. Receipts are immutable, Ed25519-signed records of a routing or payment event. Use to verify what was paid, to whom, for what capability, and what the on-chain settlement reference is. IDs start with rcpt_ (Phase 3) or rrcpt_ (Phase 4). Output: returns the signed receipt envelope as JSON. Phase 3 (rcpt_) returns a SignedReceipt with receipt (call metadata + settlement ref) and signature (Ed25519 over JCS-canonicalized receipt body). Phase 4 (rrcpt_) returns {receipt, signature} where receipt.paid contains routing details and signature covers the canonical envelope. To verify an envelope offline use the verify_receipt tool with the returned JSON, or @trustbench/verify-receipt npm.
verify
verify_receipt
Verify the Ed25519 signature on a TrustBench receipt. Two modes: (1) Lookup mode — pass receipt_id and the server fetches the receipt from trustbench.io and re-runs verification (handy when you only have an ID). (2) Offline mode — pass receipt_json (the full {receipt, signature} envelope an agent received from a third party) and the server verifies the Ed25519 signature against the published public key at trustbench.io/.well-known/trustbench-pubkey without trusting the database. Exactly one of receipt_id or receipt_json must be provided. Output: returns JSON with receipt_id, signature_valid (boolean), on_chain_verified (boolean, where present), signature_alg ("ed25519"), verify_url, pubkey_url. For non-server-mediated verification with no network round-trip, use the @trustbench/verify-receipt npm package.

Endpoints

URLTransportStateLatencyChecked
https://trustbench.io/mcp streamable-http answering 356 ms 5 min ago

TrustBench — questions

Answers built from our own checks of this server.

What can TrustBench do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_rankings, get_receipt, verify_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TrustBench working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 327 ms. The bar chart above shows every period we have measured.
How do I connect TrustBench?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TrustBench need an API key?
No. TrustBench completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is TrustBench?
It answers our handshake in 327 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use TrustBench?
The npm package @trustbench/mcp was installed 37 times in the last week. Week over week that is +16%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is TrustBench open source?
Yes — written in TypeScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.