x402 Notary MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOTARY_RAIL | No | Blockchain rail to use: 'base' or 'solana'. Default is 'base'. | base |
| NOTARY_BASE_URL | No | Base URL for the notary API. For solana rail, set to https://notary-solana.forgemesh.io. For base rail, defaults to https://notary.forgemesh.io. | |
| SOLANA_PRIVATE_KEY | No | Private key for a Solana wallet (JSON byte array, base58, base64, or hex-encoded). Required for notarization on Solana rail. | |
| WALLET_PRIVATE_KEY | No | Private key for a Base wallet used for x402 micropayments. Required for notarization on Base rail. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notarize_inferenceA | Get a cryptographic receipt for one AI inference. Returns a signed Ed25519 attestation, sha256 content hash, and Merkle chain-anchor status for {prompt, response, model_id}. The notary does NOT store your prompt or response — only the hash is retained. Costs $0.001 USDC via x402 (requires WALLET_PRIVATE_KEY for Base or SOLANA_PRIVATE_KEY for Solana). |
| notarize_batchA | Notarize up to 20 AI inferences in one call — one signed attestation per record. Ideal for audit trails and agent pipelines. Costs $0.005 USDC via x402 (requires WALLET_PRIVATE_KEY for Base or SOLANA_PRIVATE_KEY for Solana). |
| verify_attestationA | FREE — verify any attestation issued by the notary. Supply the attestation_id plus either the original content ({prompt, response, model_id}) or its content_hash. Returns the Ed25519 signature check, hash comparison, and a Merkle inclusion proof once the batch is sealed. No wallet needed. |
| get_receiptA | FREE — fetch the public receipt for an attestation: content hash, model, timestamps, Ed25519 signature, and Merkle anchor proof. Raw prompt/response are never stored, so receipts contain proof material only. No wallet needed. |
| notary_statsA | FREE — live aggregate stats: total notarizations, 24h volume, top models by attestation count, sealed/anchored Merkle batches. No wallet needed. |
| notary_pubkeyA | FREE — the notary's Ed25519 public key (base64, raw 32 bytes) for fully offline signature verification. No wallet needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: creating receipts (single or batch), retrieving receipts, verifying attestations, viewing stats, and obtaining the public key. There is no overlap or ambiguity between them.
Naming conventions are mixed: three tools use 'notarize' verbs, two use 'notary_' prefix, and others use 'get_receipt' and 'verify_attestation'. While each name is descriptive, the lack of a uniform pattern creates some inconsistency.
Six tools is well-scoped for a notary service, covering creation, retrieval, verification, stats, and key management without bloat or gaps.
The surface covers the full lifecycle: notarize (single/batch), fetch receipt, verify, and obtain public key for offline verification. No obvious missing operations for the domain.