TrustBench MCP server

• get_rankingsFree

  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).

• get_receiptFree

  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_receiptFree

  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.

• Code scan3 source files scanned25/25
• Live reliabilityremote reachable in 637ms20/20
• Tool poisoning3 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

93/100

higher than 96% of 1,761 Finance servers

Tools

3

the typical Finance server has 8

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote Finance server answers 100%

Response time

226 ms

faster than 61% of 1,133 Finance servers

TrustBench: common questions

Is TrustBench MCP server safe?

Yes, by our scan: it is graded A (93/100). Read the TrustBench safety report

How do I install TrustBench?

It runs remotely at trustbench.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does TrustBench need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is TrustBench maintained?

The last commit was 38 days ago (2026-09-26). The latest release is v1.1.1.

Is TrustBench up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of TrustBench?

Servers from other publishers that do the same job: three.ws Agent Payments MCP server, X402 List MCP server and Pulsefeed X402 MCP server.

How does TrustBench compare with other Finance MCP servers?

safety score 93/100 (higher than 96% of 1,761 Finance servers); tools 3 (the typical Finance server has 8); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.