x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).
Most payments and commerce work still happens through a UI a human drives. TrustBench MCP server moves it into the conversation instead. x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).
Verify that x402 payments settled on-chain and get cryptographically signed proof. POST /verify with a receipt ID or raw envelope to confirm Ed25519 signature validity + on-chain settlement on Base, no trust required.
The server publishes 9 tools. What each one is for:
Ed25519 — signed scorecards, public key at /.well-known/trustbench-pubkeyx402 — paywalled API endpoints (per-call USDC pricing surface)get_rankings — scored providers by capability. No API keyget_receipt — fetch any receipt by ID (rcpt_… / rrcpt_…). No API keyverify_receipt — confirm Ed25519 signature + on-chain status. No API keyServer — enforced spend caps (the agent must enforce caps locally if it cares)Per-paying — wallet hourly rate limit.** Default 60 paid calls per hour per agent_address. Tunable via TRUSTBENCH_PAYWALL_HOURLY_LIMIT (set to 0 to disable)Idempotency — key replay with replayed_at marker.** Idempotency-Key header (16-128 chars) honored on every paywalled call. Same key + same body within 24 hoursSingle — merchant routing.** POST /route serves one capability against one selected provider per call. Multi-merchant fan-out (one intent → multiple paid APIsThe server ships on npm as @trustbench/verify-receipt, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. TrustBench's toolset — Ed25519, x402, get_rankings and 6 more — is a fair guide to whether it matches your workflow.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Ed25519 | signed scorecards, public key at /.well-known/trustbench-pubkey |
| x402 | paywalled API endpoints (per-call USDC pricing surface) |
| get_rankings | scored providers by capability. No API key. |
| get_receipt | fetch any receipt by ID (rcpt_… / rrcpt_…). No API key. |
| verify_receipt | confirm Ed25519 signature + on-chain status. No API key. |
| Server | enforced spend caps (the agent must enforce caps locally if it cares). |
| Per-paying | wallet hourly rate limit.** Default 60 paid calls per hour per agent_address. Tunable via TRUSTBENCH_PAYWALL_HOURLY_LIMIT (set to 0 to disable). Returns 429 with Retry-After: 60 when exceeded. |
| Idempotency | key replay with replayed_at marker.** Idempotency-Key header (16-128 chars) honored on every paywalled call. Same key + same body within 24 hours returns the original signed receipt with a top-level replayed_at field add |
| Single | merchant routing.** POST /route serves one capability against one selected provider per call. Multi-merchant fan-out (one intent → multiple paid APIs → one envelope) is Phase 4. |
{
"mcpServers": {
"trustbench": {
"command": "npx",
"args": ["-y", "@trustbench/mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.