xProof MCP Server

by jasonxkensei Your server? Claim it

not responding

xProof is listed as active in the registry but did not answer our last check. It exposes 13 tools. Last commit 27 Sep 2026.

Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.

Uptime history 91 days of history · worst day 0%

91 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

623 ms

Response time

average over 24h

Stars

last commit 27 Sep 2026

xProof does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add xproof --transport http https://xproof.app/mcp

Settings → Connectors → Add custom connector, then paste this address

https://xproof.app/mcp

~/.codex/config.toml

[mcp_servers.xproof]
url = "https://xproof.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "xproof": {
      "url": "https://xproof.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "xproof": {
      "type": "http",
      "url": "https://xproof.app/mcp"
    }
  }
}

Available tools 13

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

certify

certify_file

Create a blockchain certification for a file. Records the SHA-256 hash on MultiversX blockchain as immutable proof of existence and ownership. Cost: $0.01 per certification, paid in EGLD.

certify_with_confidence

Create a staged blockchain certification with a confidence score. Use this when your decision builds progressively — certify at 60% (initial assessment), 80% (pre-commitment), and 100% (final decision). Each stage shares the same decision_id, creating an on-chain audit trail of the decision process. Governance: set reversibility_class='irreversible' for actions that cannot be undone — xproof will flag a policy violation if confidence_level < 0.95. Cost: $0.01 per certification.

attestations

check_attestations

Check domain-specific attestations for an AI agent wallet on xproof. Returns active attestations issued by third-party certifying bodies (healthcare, finance, legal, security, research). Each active attestation adds +50 to the agent's trust score (max +150 from 3 attestations). Use this to verify an agent's credentials before delegating a sensitive task.

audit

audit_agent_session

Certify an AI agent's work session on the MultiversX blockchain BEFORE executing any critical action (trade, deploy, data access). Returns a proof_id compliance certificate. The agent MUST call this tool before acting — certification failure blocks execution. Governance: set reversibility_class='irreversible' for actions that cannot be undone — a policy violation is flagged if confidence_level < 0.95 on irreversible decisions. Schema: https://xproof.app/.well-known/agent-audit-schema.json

calibration

get_calibration

Query an agent's calibration quality over time: mean confidence gap, variance, bias label (overconfident / underconfident / calibrated), and per-decision time series. Fully public — use this to evaluate another agent before trusting it. agentId accepts a MultiversX wallet address (erd1...) or internal user id.

coherence

check_coherence

Anchor your agent's reasoning as an immutable WHY proof BEFORE executing an action. Implements the Prove Before Act / Coherence Layer pattern. Pass intent (goal), context (facts considered), and decision (action about to execute). Receives: proof_id, coherence_anchor (SHA-256 of the payload), timestamp. Link the returned proof_id to your WHAT proof via certify_file metadata.why_proof_id to complete the full 4W audit trail. Cost: $0.01 per anchor (same as certify_file).

discover

discover_services

Discover available xproof certification services, pricing, and capabilities. No authentication required.

investigate

investigate_proof

Reconstruct the full 4W audit trail for a contested agent action. Returns WHO (agent identity + SIGIL), WHAT (SHA-256 hash on-chain), WHEN (MultiversX block timestamp), WHY (decision chain anchored before acting). Includes verification summary with intent_preceded_execution flag, chronological timeline of WHY/WHAT proofs, and session heartbeat anchor. Requires x402 payment ($0.01 USDC on Base via X-PAYMENT header) or API key authentication. Without payment, returns payment requirements with USDC address and amount.

proof

get_proof

Retrieve a proof in structured JSON or Markdown format. Use JSON for machine processing, Markdown for LLM consumption.

register_trial

START HERE if you have no API key. Get 10 free on-chain certifications instantly — no wallet, no credit card, no account required. Call this once with any agent_name, receive a pm_ key, then use certify_file or audit_agent_session immediately. Takes under 1 second.

require

require_coherence_anchor

Policy gate: verify a valid, unexpired coherence anchor (WHY proof) exists for a given intent BEFORE allowing an action to execute. Call this from an orchestrator before delegating a sub-action. Pass either the exact intent_hash (the coherence_anchor returned by check_coherence) or the same intent + context + decision payload (the anchor hash is recomputed deterministically). Returns { allowed, anchor_id, expires_at }. If allowed=false, block execution and call check_coherence first. Free — no credit consumed.

submit

submit_outcome

Submit the actual outcome for a decision previously anchored with metadata.confidence_level. Computes the confidence gap (anchored − actual) and stores it for calibration tracking. Operator-only — you must own the proof. Each proof can only have one outcome.

verify

verify_proof

Verify an existing xproof certification. Returns proof details including file hash, timestamp, blockchain transaction, and verification status.

Endpoints

URL	Transport	State	Latency	Checked
https://xproof.app/mcp	streamable-http	answering	623 ms	3 min ago

Alternatives to xProof

same job, measured the same way

Privi Anchor

by canoydario847-cloud

Hash anchoring and proof-of-existence on chain for AI agents and apps. Free with an API key.

4 tools answering

Proctor

by louissarvin

Human oversight for AI agents: block a tool call on a verified human, with on-chain proof.

37 installs/wk local only

Agentseal

by joeybrar

Verifiable action logs for AI agents. Every action is recorded in a SHA-256 hash chain.

42 installs/wk local only

Dokimo MCP

by ypratap11

Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.

3 tools answering

Hashproof

by csacanam

Issue verifiable credentials from AI agents for $0.10 via x402. On-chain on Celo, IPFS-pinned.

62 installs/wk local only

Vaultfire Trust Protocol

by ghostkey316

On-chain trust verification and Street Cred for AI agents. ERC-8004, multi-chain.

62 installs/wk local only

Wayreceipt

by pages-wayreceipt

Proof of delivery for agent work: verify countersigned receipts and deliverable hashes. Free.

4 tools answering

ViBo Memory

by vnbochkarev-netizen

Local-first memory for AI agents: facts with hash-chain provenance, verified recall.

local only

xProof — questions

Answers built from our own checks of this server.

What can xProof do?

It exposes 13 tools, read directly from the server on our last check. Among them: audit_agent_session, certify_file, certify_with_confidence, check_attestations, check_coherence, discover_services and 7 more. 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 xProof working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 623 ms. The bar chart above shows every period we have measured.

The registry lists xProof as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect xProof?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does xProof need an API key?

No. xProof completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.

Is xProof open source?

We cannot say either way: written in TypeScript and 1 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.