Skip to main content
Glama
AOTrust - PDR Notarization

AOTrust - PDR Notarization

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
notary_quoteA

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.

notary_freeA

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).

notary_notarizeA

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.

notary_verifyA

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'.

notary_notarize_paidA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 5 tools

Disambiguation3/5

Most tools are distinct, but notary_notarize and notary_notarize_paid both perform paid notarisation on different payment rails, and the generic name notary_notarize can be mistaken for the default paid path. The descriptions clarify the quote/pay/notarize/verify flow, but the overlap still risks misselection.

Naming Consistency4/5

All tools consistently use the notary_ prefix and action-oriented suffixes, which is predictable. However, notary_notarize vs notary_notarize_paid is slightly misleading because notary_notarize is itself a paid NEAR_DIRECT path, not the general or free operation.

Tool Count5/5

Five tools are well-scoped for a focused notarisation workflow: free proof, quote, two paid notarisation rails, and verification. Each tool has a clear role in the lifecycle.

Completeness4/5

The surface covers the core lifecycle of quote, payment, notarisation, and verification, plus a free proof path. Minor gaps include no direct retrieval of paid PDRs by a shield_id or listing of past notarisation jobs, but these are workarounds rather than critical dead ends.

Maintenance

ActivityActive
ResponsivenessNo recent community issues