mcpbeat Sign in

AOTrust Notarization & Evidence Server MCP Server

answering

AOTrust Notarization & Evidence Server is answering right now. Last checked 5 min ago. 223 installs a week from pypi. It exposes 5 tools. Last commit 8 Oct 2026.

Cryptographic proof of existence for AI agents. x402 on Base or Solana, NEAR anchored. Free tier.

Installs per day peak 490 · avg 61 · -31% w/w
a month agotoday
Uptime history 22 days of history · worst day 99%
22 days agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
183 ms
Response time
average over 24h
223
Installs / week
npm and PyPI

What the code does

We read the source, 7 d ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

File ships in the package but is absent from the source [пакет] agent_notary/__init__.py:1, [пакет] agent_notary/client.py:1, [пакет] agent_notary/exceptions.py:1 и ещё 2
этот файл ставится пользователю, но в репозитории его нет

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add notary --transport http https://api.aotrust.link/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "notary": {
      "url": "https://api.aotrust.link/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.notary]
url = "https://api.aotrust.link/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "notary": {
      "url": "https://api.aotrust.link/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "notary": {
      "url": "https://api.aotrust.link/mcp"
    }
  }
}

This one needs environment variables set before it will start: AOTRUST_BASE_URL (AOTrust API base URL). The author declared them in the registry entry; get the values from the project itself.

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

notary
notary_free
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_notarize
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. Returns job_id — use notary_verify to poll for the signed PDR. Step 3 of the notarisation flow: quote -> pay -> notarize -> verify.
notary_notarize_paid
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.
notary_quote
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_verify
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'.

Endpoints

URLTransportStateLatencyChecked
https://api.aotrust.link/mcp streamable-http answering 187 ms 5 min ago

Alternatives to AOTrust Notarization & Evidence Server

same job, measured the same way
AOTrust Notarization & Evidence Server
by gitserge-crypto

Cryptographic proof of existence for AI agents. Base x402, NEAR anchored. Free tier.

local only
x402 Notary MCP
by forgemeshlabs

Cryptographic receipts for AI outputs on Base or Solana via x402.

275 installs/wk local only
T
TrustNotch
by trustnotch

Tamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles.

105 installs/wk local only
x402 Merchant Check
by gradientdecisions

Pre-payment merchant trust checks for x402 agents on Base and Solana.

1 tools answering
X402 Endpoints
by digitalweb33333-creator

x402 paid API tools for AI agents on Base: EU/global registries, crypto, wallet & agent trust.

52 tools answering
Xenarch MCP
by xenarch-ai

Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.

83 installs/wk local only
Spraay X402 MCP
by plagtech

MCP server for Spraay x402 Gateway. 60 tools for crypto payments, DeFi, and AI on Base.

29 installs/wk local only
Cryptobuddy
by com-cryptobuddy

Australian crypto exchange intelligence for AI agents, with x402 payments on XRPL and Base.

2 tools answering

AOTrust Notarization & Evidence Server — questions

Answers built from our own checks of this server.

What can AOTrust Notarization & Evidence Server do?
It exposes 5 tools, read directly from the server on our last check. Among them: notary_free, notary_notarize, notary_notarize_paid, notary_quote, notary_verify. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AOTrust Notarization & Evidence Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 183 ms. The bar chart above shows every period we have measured.
How do I connect AOTrust Notarization & Evidence Server?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AOTrust Notarization & Evidence Server need an API key?
No. AOTrust Notarization & Evidence Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AOTrust Notarization & Evidence Server?
It answers our handshake in 183 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use AOTrust Notarization & Evidence Server?
The pypi package aotrust-protocol was installed 223 times in the last week. Week over week that is -31%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is AOTrust Notarization & Evidence Server open source?
Yes — it is published under the MIT licence, written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.