XProof MCP Server

Connect XProof to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs. The xproof mcp server is what makes that connection.

What the server does

Trust primitive for AI agents & humans on MultiversX

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Field — Type
• file_hash — string
• filename — string
• author_name — string
• webhook_url — string
• Method — Endpoint
• POST — /api/keys
• GET — /api/keys
• DELETE — /api/keys/:id
• Verification — The Verification tool exposed by this server
• Webhooks — When a proof is anchored on-chain, xProof sends a POST to your webhook_url with HMAC-SHA256 signature in the X-Webhook-Signature header. Retry
• Authentication — The Authentication tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: XPROOF_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. XProof's toolset — Field, file_hash, filename and 9 more — is a fair guide to whether it matches your workflow. It is maintained by jasonxkensei; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch XProof.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.