# TrustBench MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-lithvall-trustbench
- Repository: https://github.com/lithvall/TrustBench

## Install
- Command: `npx -y @trustbench/mcp`
- Endpoint: https://trustbench.io/mcp
- Auth: Not captured

## Setup notes
- Package: Npm @trustbench/mcp v1.1.1
- Remote endpoint: https://trustbench.io/mcp

## Tools
- 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). Endpoint: https://trustbench.io/mcp
- 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. Endpoint: https://trustbench.io/mcp
- 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. Endpoint: https://trustbench.io/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.lithvall
- Version: 1.1.1
- Runtime: Npm
- Transports: STDIO, HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 15, 2026
- Source: https://registry.modelcontextprotocol.io