Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,549Letters: 14Defects: 1,323counted 4 min ago
teppi

Server definition

Hash
sha256:ed533bdf2472aa1429f8b19d237152bb06d413bb6f02e9d988a910bd348fd4a5
What it is
What a remote MCP server returned when asked what it offers: 3 tools

The blob, as servednamed by its sha256

{ "instructions": null, "tools": [ { "description": "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).", "inputSchema": { "properties": { "capability": { "description": "The provider capability to query rankings for.", "enum": [ "search", "inference", "data", "media", "infra" ], "type": "string" } }, "required": [ "capability" ], "type": "object" }, "name": "get_rankings", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "receipt_id": { "description": "The receipt ID, e.g. rcpt_01KQY7C44GAPSXZPFQYRZ1D10C or rrcpt_…", "type": "string" } }, "required": [ "receipt_id" ], "type": "object" }, "name": "get_receipt", "outputSchema": null }, { "description": "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.", "inputSchema": { "oneOf": [ { "required": [ "receipt_id" ] }, { "required": [ "receipt_json" ] } ], "properties": { "receipt_id": { "description": "Lookup mode: the receipt ID to fetch and verify. Mutually exclusive with receipt_json.", "type": "string" }, "receipt_json": { "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.", "type": "object" } }, "type": "object" }, "name": "verify_receipt", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:ed533bdf2472aa1429f8b19d237152bb06d413bb6f02e9d988a910bd348fd4a5 | sha256sum