X402 Notary MCP vs Emilia Protocol
A side-by-side look at the X402 Notary MCP and Emilia Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose X402 Notary MCP for security work as a local process; choose Emilia Protocol for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose X402 Notary MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WALLET_PRIVATE_KEY, NOTARY_RAIL, NOTARY_BASE_URL, SOLANA_PRIVATE_KEY. - You want tools like
notarize_inference, notarize_batch, verify_attestation.
Choose Emilia Protocol when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
ep_guard_action, ep_check_signoff, ep_verify_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 63/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | WALLET_PRIVATE_KEYNOTARY_RAILNOTARY_BASE_URLSOLANA_PRIVATE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 599 |
| Directory activity | 2 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 6 | 3 |
| Full listing | View X402 Notary MCP | View Emilia Protocol |
Tools & capabilities
X402 Notary MCP tools 6
notarize_inferenceGet 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 a Base wallet).notarize_batchNotarize 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 a Base wallet).verify_attestationFREE — 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_receiptFREE — 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_statsFREE — live aggregate stats: total notarizations, 24h volume, top models by attestation count, sealed/anchored Merkle batches. No wallet needed.notary_pubkeyFREE — the notary's Ed25519 public key (base64, raw 32 bytes) for fully offline signature verification. No wallet needed.
Emilia Protocol tools 3
ep_guard_actionRequest authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.ep_check_signoffPoll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.ep_verify_receiptAsk the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
X402 Notary MCP
{
"mcpServers": {
"forgemeshlabs-x402-notary-mcp": {
"command": "npx",
"args": [
"-y",
"@forgemeshlabs/x402-notary-mcp"
],
"env": {
"WALLET_PRIVATE_KEY": "YOUR_WALLET_PRIVATE_KEY_HERE",
"NOTARY_RAIL": "YOUR_NOTARY_RAIL_HERE",
"NOTARY_BASE_URL": "YOUR_NOTARY_BASE_URL_HERE",
"SOLANA_PRIVATE_KEY": "YOUR_SOLANA_PRIVATE_KEY_HERE"
}
}
}
}
Emilia Protocol
{
"mcpServers": {
"emiliaprotocol-emilia-protocol": {
"command": "npx",
"args": [
"-y",
"@emilia-protocol/mcp-server"
]
}
}
}
Frequently asked questions
X402 Notary MCP is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick X402 Notary MCP for security work and Emilia Protocol for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
X402 Notary MCP has no declared pricing — check the project's own site. Emilia Protocol is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add forgemeshlabs-x402-notary-mcp and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, X402 Notary MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Emilia Protocol has 71/100 (Great) with 6 views, 0 installs and 599 GitHub stars.