AOTrust issues cryptographic PDRs (Provenance Data Records) — proving a digital artifact existed at a specific time. $0.01 per proof. Blockchain-anchored. Publicly verifiable.
Scored across 5 tools
Most tools have clearly distinct roles in the quote -> pay -> notarize -> verify flow. The main ambiguity is between notary_notarize and notary_notarize_paid, since both create notarizations, though their payment paths are described as different.
All tools use a consistent snake_case notary_ prefix and are generally action-oriented. The exception is notary_free, which uses an adjective/mode rather than a verb, and notary_notarize_paid is slightly verbose but still readable.
Five tools are well-scoped for a notarization workflow: free proof, quote, two paid notarization paths, and verification. Each tool earns its place without excessive surface area.
The core notarization lifecycle is covered, including quoting, paying/notarizing, verifying, and a free proof mode. Minor gaps exist, such as no dedicated tool to verify a free shield_id or list previous notarizations, but core workflows are supported.
Create a free cryptographic proof of existence (PDR) for a digital artifact without payment. Dual mode: pass work_hash (Mode A, client-computed SHA-256 hex) OR content (Mode B, raw text/code ≤60KB — server hashes it, zero retention). Subject to rate limits (5/IP/day, 1000/day global). Returns shield_id, pdr_b64, and verify_url. For on-chain settlement proof, use notary_notarize_paid ($0.01 USDC on Base).
Inputs: content, metadata, work_hash, prev_work_hash. Returns: object
Submit a work artifact for on-chain notarisation (NEAR_DIRECT payment path). PREREQUISITE: Send the NEAR amount from notary_quote to the sink account, then provide the resulting tx_hash here. The server verifies the on-chain payment and submits the notarisation. Payment binding: pass payer_account (the NEAR account that paid) and bind_sig — a base64 Ed25519 NEP-413 signature over 'AOTrust AITP-BIND v1 work_hash:<64hex> tx_hash:<tx_hash>'. Returns job_id — use notary_verify to poll for the signed PDR. Step 3 of the notarisation flow: quote -> pay -> notarize -> verify.
Inputs: tx_hash (required), work_hash (required), bind_sig, metadata, +4 more. Returns: object
Notarize a work hash on AOTrust (mainnet NEAR + Base USDC receipt). $0.01 USDC via x402-over-MCP: call without payment to receive PaymentRequired; retry with params._meta['x402/payment'] = signed PaymentPayload (EIP-3009, scheme exact, eip155:8453). HTTP clients: POST /notarize with x-payment header.
Inputs: work_hash (required), agent_sig, agent_pubkey, prev_work_hash. Returns: object
Request a notarisation quote for a work artifact. Returns the cost ($0.01 USDC or NEAR equivalent), a quote_id valid for 600 seconds, the sink account to send payment to, and the PDR schema version. Step 1 of the notarisation flow: quote -> pay -> notarize -> verify.
Inputs: work_hash, pdr_version. Returns: object
Verify a notarisation by job_id. Returns status (pending/anchored/error). If anchored, returns the full PDR record (base64, 239 bytes) with Ed25519 signature verification. Step 4 of the notarisation flow: quote -> pay -> notarize -> verify. Can be polled repeatedly until status changes from 'pending' to 'anchored'.
Inputs: job_id (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.