TrustBench

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

我該用這個嗎

品質與安全性

A
說明品質
100%
結構描述完整度
97%
命名品質
100%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~825Token(工具定義)
~864 B典型回應大小
中等的注意力影響(128k 上下文的 0.64%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "trustbench": {
      "command": "npx",
      "args": [
        "@trustbench/mcp"
      ]
    }
  }
}

可執行的套件

npm@trustbench/mcp1.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"
      ]
    }
  ]
}

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本3 個工具
已驗證未記錄版本3 個工具