MCP tool reference · #562 of 563 by publishers
verify_attestation
Exposed by 8 servers from 8 publishers, read from the live servers by the Serverdex check; 37.5% of them take a attestation parameter; the most-starred is DataPulse (3 stars).
verify_attestation(attestation: string, …)Parameters
share = % of the 8 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| attestation | string | 37.5% | 100% | The attestation as JSON text: either the whole response from attest_page or just its `attestation` object. |
| attestation_json | string | 12.5% | 100% | The full Zetesis attestation object, as JSON text. |
| hash | string | 12.5% | 100% | SHA-256 of the artifact you want to check, as hex. Hash the bytes you actually hold — if they were modified after attestation, the digest won't match any record |
| message | string | 12.5% | 100% | The exact `message` string from the attestation, newlines and all. |
| reference | string | 12.5% | 100% | Dataset slug returned by search_datasets or an exact published digest reference, e.g. 'fuelprice'; the slug resolves through the attestation index. |
| replay_chain | boolean | 12.5% | 0% | Set true to perform the slower L2 daily-head replay to a Git tag, e.g. true; omit it to run L1 only. |
| signature | string | 12.5% | 100% | The `signature` from the attestation, 0x-prefixed. |
| token | string | 12.5% | 100% | attestation.token from evaluate_deliverable |
Source: the input schema each server returns for verify_attestation, aggregated over the 8 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with verify_attestation
8 of 8 · 8 publishers · 8 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes verify_attestation |
|---|---|---|---|---|---|---|
| 1 | DataPulser3dz4r · Data & Analytics | r3dz4r | Data & Analytics | 3 | yes | Use to verify a signed published probe attestation after an evidence audit. Returns L1 signature, key, time, and chain-link checks; optional L2 replay of daily heads to a Git-tag anchor; and L3 scope, which requires verify_evidence for live transport. A valid signature proves attestation integrity and scope, not upstream semantic truth or currentness. For a deep audit use search_datasets → get_evi |
| 2 | Lazarettojamesdfinance-dev · Security & Identity | jamesdfinance-dev | Security & Identity | 2 | yes | Verify a Lazaretto scan attestation that another agent (or a README, or a lockfile) handed you, WITHOUT re-scanning or paying. Free and anonymous. Returns signature validity and the signed claims, including verdict, risk and subject. For a clear or flagged SHA-256 subject only, checks the current known-bad indicator set and includes `contradicted` when it matches. That field is otherwise omitted; |
| 3 | Patinaramakrishnanhulk20 · Other | ramakrishnanhulk20 | Other | 1 | yes | Check whether a Patina attestation really was signed by Patina. Every Patina score ships with an EIP-191 signed message; hand this tool that `message` and `signature` and it returns the address it recovered, the address Patina publishes, and whether the two match. IMPORTANT, AND THE WHOLE POINT: you do not need this tool, and where you can, you should not use it. A signature is worth something pre |
| 4 | Tollkitultrastarz · Search & Web | ultrastarz | Search & Web | — | yes | Free, forever, no account. Hand back an attestation -- yours or one someone else gave you -- and find out whether the signature holds and whether we issued it. Works on attestations this service did not produce: the answer for those is a clear no, which is the point. Holds no database, so it keeps working whoever is running it. When to use: Someone handed you an attestation, or you want to check |
| 5 | Hubminmaxnn · Other | minmaxnn | Other | — | yes | Verify an attestation made by attest_deliberation: checks its EdDSA signature against this site's signing key and returns the decoded payload with issuer and issue time. Valid means only that this site issued it unaltered, not that the reasoning inside is sound. Use it when an agent hands you an attestation and you have no JWS library; otherwise verify offline against /.well-known/attestation-keys |
| 6 | Novarithm Agent Hub: trust and commerce checkssalimyou91 · AI & Agents | salimyou91 | AI & Agents | — | yes | [PAID $0.001 USDC/call, x402, eip155:8453] Verify an attestation token issued by evaluate_deliverable: recovers the EIP-712 signer, checks it is our evaluator, returns verdict, score, jobId and the bytes32 reason. |
| 7 | Zetesis Scientific Due Diligencereutavidan · Health & Science | reutavidan | Health & Science | — | yes | Verify a Zetesis attestation, confirming an evaluation's claim, evidence, and conclusion have not been altered since it was signed. Use when someone has a Zetesis dossier or attestation and wants to independently re-check it. Args: attestation_json: the full attestation object as JSON text. |
| 8 | Kamykamy-development · Documents & Knowledge | kamy-development | Documents & Knowledge | — | yes | Ask Kamy whether a SHA-256 digest has an attestation on record — the tool that actually returns a verdict. Takes a digest, not a file: if what you hold is a PDF, run verify_pdf_signature over the bytes first and pass the sha256 it gives you. A match returns { verified: true, artifact_type, recorded_at, signature, public_key }. A false result means no attestation exists for those exact bytes, which |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.