AOTrust Notarization & Evidence Server

Name: AOTrust Notarization & Evidence Server
Author: GitSerge-crypto

by GitSerge-cryptoversion 2.5.0i★ –iRuns on your computer

Registry namelink.aotrust/notary

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: AOTRUST_BASE_URL

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "notary": {
      "command": "uvx",
      "args": [
        "aotrust-protocol"
      ],
      "env": {
        "AOTRUST_BASE_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add notary --env AOTRUST_BASE_URL=your-value -- uvx aotrust-protocol

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "notary": {
      "command": "uvx",
      "args": [
        "aotrust-protocol"
      ],
      "env": {
        "AOTRUST_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "notary": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "aotrust-protocol"
      ],
      "env": {
        "AOTRUST_BASE_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

AOTRUST_BASE_URL env
AOTrust API base URL

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain aotrust.link (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32520 servers in this category
Published to the registry more recently than 73% of the other 32520 servers in this category
Basic checks equal to or better than 100% of the other 32520 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is AOTrust Notarization & Evidence Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.5.0) reached the registry 13 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Toggl 2.0

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Toggl 2.0

by toggl

Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

AOTrust — Cryptographic Proof of Existence for AI Agents

AOTrust issues PDRs (Provenance Data Records) — 239-byte cryptographic receipts proving a digital artifact existed at a specific time. $0.01 USDC via x402 — pay on Base (EVM) or Solana (SVM, via MCP). Anchored hourly to NEAR blockchain. No account needed. Supports ordinary (v0x03) and bilateral (v0x04) signatures.

Positioning: an Independent External Provenance Checkpoint. Native attestations (Sigstore, GitHub artifact attestations) verify a build *inside* the CI system that produced it. AOTrust complements them: it issues a signed certificate *outside* GitHub/Microsoft infrastructure and anchors it hourly to the NEAR blockchain — so provenance survives even if the repository is rewritten, the CI logs disappear, or the attestation store is unavailable. Use both.

Agent Checkpoint (new)

Connect your AI coding agent in 60 seconds and make it notarize plan/patch/release checkpoints — free tier, no account: [agent-checkpoint/](agent-checkpoint/) — mcp.json drop-ins for Cursor, Cline, and any MCP client, plus a copy-paste AGENTS.md block (Provenance: in commits).

Authorship Claims (bilateral signatures)

Beyond agent workflows, AOTrust supports bilateral PDRs (v0x04): the artifact is signed by you (Ed25519) *and* countersigned by the notary — a binding hash ties your public key to the content. This turns "I wrote/published this first" into a verifiable claim for any digital artifact: manuscripts, designs, photos, research notes, legal correspondence. Verification is public at https://verify.aotrust.link — no account, no software install for the reader. Signing guide (Ed25519, NEP-413): SKILL.md → Bilateral Signature. See pdr-spec.md §v2.4 for the binding-hash construction.

Quickstart

Prefer one-click? See INTEGRATIONS.md — ready MCP configs for Cursor, Windsurf, Cline, Claude Desktop, plus a "notarize before commit" rule for your assistant and LangChain/CrewAI examples.

# 1. Compute SHA-256 hash of your artifact

HASH=$(echo -n "Hello AOTrust" | sha256sum | cut -d' ' -f1)

2. Request notarization → get 402 payment details

curl -X POST https://api.aotrust.link/notarize \ -H "Content-Type: application/json" \ -d "{\"work_hash\":\"$HASH\",\"agent_sig\":\"\",\"agent_pubkey\":\"\"}"

3. Pay $0.01 USDC on Base (EIP-3009), then POST with x-payment header

Full example: see SKILL.md → "Step 3: Pay"

For full EIP-3009 signing code (Python + ethers.js examples), see SKILL.md.

Interfaces

Interface	Best for	Auth
HTTP API	Developers, scripts, CI/CD	x402 payment (no API key needed); free tier 5/day/IP
MCP	AI agents (Claude, Cursor, Cline)	None for discovery + free tools (notary_free 5/day/IP)

Authentication & keys

Notarization is keyless. Standard notarization (free tier and x402 micropayments) never requires an API key — payment is in-band (x402 x-payment header) and free calls are IP rate-limited.

AO_TRUST_KEY is optional and only used by the GitHub Action (action/notarize.py) to unlock the dedicated CI rate limit (50/24h per key, via X-Api-Key on /v1/shield/free) instead of the shared per-IP free limit (5/24h). It is an opt-in convenience for CI pipelines — nothing else reads it, and no secret ever enters a PDR.

Endpoints:

API: https://api.aotrust.link/notarize
MCP: https://api.aotrust.link/mcp
Verify: https://verify.aotrust.link
Docs: https://docs.aotrust.link

Verify API (public, embeddable)

Verification is a standalone public API — no account, no rate limits, no payment. Embed it in your product (dashboards, audit tools, escrow flows) or call it from the terminal:

# Verify a PDR (base64url-encoded bundle):

curl https://api.aotrust.link/v1/pdr/verify/

→ {"valid": true, "checks": {...}, "error": null}

Look up a PDR by Shield ID (8 hex chars):

curl https://api.aotrust.link/v1/shield/lookup/

→ {"found": true, "pdr_b64": "...", "shield_id": "..."}

Get the notary public key for offline verification:

curl https://api.aotrust.link/v1/notary/pubkey

Prefer full offline trust? pdr_parser.py verifies any PDR locally — zero dependencies, no network, no trust in our servers.

Offline Merkle verification (anchored receipts)

Anchored PDRs carry the hourly Merkle root committed on-chain in the NEAR contract notary-node.near — readable from any public NEAR RPC, forever, independent of our servers. The verify API returns merkle_proof, merkle_index, merkle_leaf and merkle_tree_size for anchored PDRs. Save the verify JSON response — then verify it forever, offline:

# (once) save the verify response when the receipt is fresh:

curl https://api.aotrust.link/v1/pdr/verify/ > verify.json

(any time, no AOTrust server needed) check inclusion:

python3 verify_merkle_inclusion.py \ --leaf --proof \ --index --root \ --tree-size

→ VALID

the root can always be re-checked against the chain itself via any

NEAR RPC: contract notary-node.near, method get_root({"seq": N})

verify_merkle_inclusion.py is standalone and zero-dependency (RFC 9162 §2.1.3.2 walk, same hashing as the anchoring engine). tree_size must be taken from the verify response (or a published anchor snapshot), not chosen by the verifier.

PDR Specification & Tools

pdr-spec.md — PDR v2.3/v2.4 binary format (Internal 193B + External 239B, ordinary + bilateral)
pdr_parser.py — standalone parser, zero dependencies, offline verification
aotrust-notarize/SKILL.md — full integration guide for AI agents

Comparison

Feature	AOTrust	Chainlink	OpenTimestamps	Notary.fyi
Price/PDR	$0.01	$0.25+	Free (slow)	$0.50+
Payment rail	x402 USDC	LINK	Bitcoin TX	Stripe
PDR format	239B binary	Oracle data	OTS file	PDF
AI agent native	MCP + HTTP	No	No	No
Blockchain anchor	NEAR (hourly)	Ethereum	Bitcoin	None
Offline verify	Yes (pdr_parser.py)	No	Yes	No

GitHub Action

Notarize build artifacts or AI-generated files directly in CI/CD — free, no wallet needed.

- uses: GitSerge-crypto/aotrust-skills@v1.1

with: files: dist/*

Outputs: shield_id, verify_url, pdr_b64. Results appear in $GITHUB_STEP_SUMMARY as a markdown table with verification links.

Example workflow

name: Release

on: release: types: [published]

jobs: notarize: runs-on: ubuntu-latest steps:

uses: actions/checkout@v4
uses: GitSerge-crypto/aotrust-skills@v1.1 with: files: dist/*
name: Show shield ID run: echo "Shield ID: ${{ steps.notarize.outputs.shield_id }}"

License

MIT

AOTrust Notarization & Evidence Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Toggl 2.0

README from the maker

AOTrust — Cryptographic Proof of Existence for AI Agents

Agent Checkpoint (new)

Authorship Claims (bilateral signatures)

Quickstart

2. Request notarization → get 402 payment details

3. Pay $0.01 USDC on Base (EIP-3009), then POST with x-payment header

Full example: see SKILL.md → "Step 3: Pay"

Interfaces

Authentication & keys

Verify API (public, embeddable)

→ {"valid": true, "checks": {...}, "error": null}

Look up a PDR by Shield ID (8 hex chars):

→ {"found": true, "pdr_b64": "...", "shield_id": "..."}

Get the notary public key for offline verification:

Offline Merkle verification (anchored receipts)

(any time, no AOTrust server needed) check inclusion:

→ VALID

the root can always be re-checked against the chain itself via any

NEAR RPC: contract notary-node.near, method get_root({"seq": N})

PDR Specification & Tools

Comparison

GitHub Action

Example workflow

License