XProof
Anchor agent-generated file hashes on MultiversX so outputs have an on-chain proof you can cite later.
Overview
xProof is a MCP server for the Ship phase that anchors file hashes on MultiversX as on-chain verifiable proofs for AI agents.
What is this MCP server?
- Streamable HTTP remote MCP at xproof.app/mcp (no local npm package in registry manifest)
- Anchors file hashes on MultiversX as verifiable on-chain proofs
- Optional Bearer API key (pm_xxx); x402 payment path works without authentication
- Version 1.2.0 proof primitive aimed at AI agent workflows
- GitHub source: jasonxkensei/xProof
- Registry version 1.2.0
- Remote endpoint https://xproof.app/mcp (streamable-http)
- Optional auth header format Bearer pm_xxx
Community signal: 1 GitHub stars.
What problem does it solve?
You cannot prove which exact file an agent produced after the fact without a tamper-evident record outside your laptop.
Who is it for?
Solo builders shipping agent-generated artifacts who want a simple MultiversX proof hook in Claude Code or Cursor.
Skip if: Teams that need full document management, private notarization without public chain exposure, or zero blockchain dependency.
What do I get? / Deliverables
After registration, stakeholders can verify file integrity against an on-chain proof tied to your attestation flow.
- On-chain proof references for anchored file hashes
- Agent-callable attest workflow via hosted MCP tools
- Verifiable integrity checks against MultiversX records
Recommended MCP Servers
Journey fit
How it compares
On-chain proof MCP integration, not a local checksum utility or agent skill.
Common Questions / FAQ
Who is XProof for?
Indie builders and AI agents that need verifiable, on-chain attestations of file hashes on MultiversX without self-hosting chain tooling.
When should I use XProof?
Use it at ship or release time when you want an auditable proof that a specific file hash was recorded before sharing or deploying.
How do I add XProof to my agent?
Register the remote MCP URL https://xproof.app/mcp in your client, add Authorization Bearer pm_xxx if you have a key, or rely on x402 payment without auth per the server schema.