TrustBench
x402 provider rankings + Ed25519-signed payment receipts + signature verification (3 tools).
我该使用它吗
质量与安全性
基于对工具定义和协议合规性的自动分析。
上下文开销
这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高，可用于其他任务的注意力就越少。
安装
一键安装
将以下内容添加到你的 `claude_desktop_config.json` 文件中：
{
"mcpServers": {
"trustbench": {
"command": "npx",
"args": [
"@trustbench/mcp"
]
}
}
}可运行的软件包
1.1.1stdio远程端点
https://trustbench.io/mcpstreamable-http它能做什么
工具清单
工具（3）
🟢get_rankings(capability)
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).
输入模式
{
"type": "object",
"properties": {
"capability": {
"type": "string",
"enum": [
"search",
"inference",
"data",
"media",
"infra"
],
"description": "The provider capability to query rankings for."
}
},
"required": [
"capability"
]
}🟢get_receipt(receipt_id)
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.
输入模式
{
"type": "object",
"properties": {
"receipt_id": {
"type": "string",
"description": "The receipt ID, e.g. rcpt_01KQY7C44GAPSXZPFQYRZ1D10C or rrcpt_…"
}
},
"required": [
"receipt_id"
]
}🟢verify_receipt(receipt_id, receipt_json)
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.
输入模式
{
"type": "object",
"properties": {
"receipt_id": {
"type": "string",
"description": "Lookup mode: the receipt ID to fetch and verify. Mutually exclusive with receipt_json."
},
"receipt_json": {
"type": "object",
"description": "Offline mode: a full signed-receipt envelope {receipt, signature} (or a Phase 3 SignedReceipt). Verified against the published Ed25519 public key without database lookup. Mutually exclusive with receipt_id."
}
},
"oneOf": [
{
"required": [
"receipt_id"
]
},
{
"required": [
"receipt_json"
]
}
]
}社区
证据