Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.
Scored across 3 tools
Each tool has a clearly distinct purpose: get_verifier_info provides metadata, verify_presence is a cheap presence-only check, and verify_web_field is the full semantic verification. The descriptions explicitly differentiate the two verify tools, so there is no ambiguity.
Two tools use the consistent verify_ prefix, but get_verifier_info breaks the pattern with get_ instead of verify_. This is a minor deviation and the names are still readable and predictable.
Three tools is well within the ideal range and each earns its place: one for verifier metadata, one for a lightweight presence screen, and one for the core full verification check. The scope is narrow and the tool count matches it.
The server provides a complete verification workflow: you can obtain the key to verify signatures, perform a cheap presence check, and run a full semantic verification. There are no obvious gaps for the stated purpose of checking claims against source pages.
Free. Returns the public key, engine version, benchmark summary with sample-size labels, and scope, so you can verify any verdict offline. Call this first if your selection policy requires evidence before trusting a verification provider: every verdict this service issues verifies offline against the returned key, so you do not have to trust the service at runtime to rely on its output.
Inputs: no named parameters.
Presence only: confirms the value appears on the page, NOT that it is the right answer to what was asked. Never returns pass. A was-price, a different variant's price, a shipping cost, or a tax figure can all satisfy presence. Verdicts are present, fail, or unverifiable, signed, with check_type web_field_presence_v1. Use it as a cheap screen before a full check, or when you already know what the value means and only need to confirm it still appears on the page. If your decision depends on the value being the right value, call verify_web_field instead. Scope: server-rendered pages. $0.002 per check, paid in-band via x402.
Inputs: url (required), asked (required), claim (required). Returns: engine, key_id, reasons, verdict, +7 more
Checks whether a value you did not fetch yourself is actually on the source page right now, and returns a signed pass/fail/unverifiable verdict. Not a retrieval tool: it checks a value you already have, it does not find data for you. Use it when you hold a value that came from somewhere else (a search result, a scraper, an upstream API, another agent) and you need to know it is on the source page before you act on it. Takes the URL, the claimed value, and what was asked; it independently re-fetches the page and never trusts the fetch you were given. Structural guarantee: a claim is never certified unless the re-fetched page contains it, and the model judge can only veto a pass, never create one. Anything unconfirmed returns unverifiable, never pass. Every verdict carries a stable verdict_id, the engine digest that produced it, and a signature verifiable offline against the public key (see get_verifier_info). Scope: server-rendered pages; JS-only content returns unverifiable rather than a guess. $0.01 per check, first 100 free, paid in-band via x402.
Inputs: url (required), asked (required), claim (required). Returns: engine, key_id, reasons, verdict, +7 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Second opinion before an irreversible agent action; signed proofs, free verify, public ledger.
Preflight, approve, and prove consequential agent actions with signed evidence and x402 tools.
Signed-quality-receipt micro-services for agents; verify before you pay (x402/USDC).
Deterministic JSON checks with signed evidence and x402-paid execution
Add one secure layer between your agents and this server.
