XProof

What xProof MCP server does

The xProof MCP server gives AI agents access to Prove Before Act, a service that anchors SHA-256 file hashes on the MultiversX blockchain. The service produces a proof record that can be checked publicly and includes a proof identifier, verification URL, certificate URL, JSON representation, and MultiversX transaction details.

This is useful for recording the existence and authorship of agent outputs without sending the original file to the service. A report, generated artifact, build output, or other file can be hashed locally and represented on-chain by its digest. Later, another party can hash the candidate file and compare it with the recorded value.

How it works

The xProof MCP server follows a hash-first workflow. An agent or application computes a SHA-256 digest locally, then submits the 64-character hexadecimal value along with metadata such as a filename and author name. Prove Before Act processes the request and returns the resulting proof status and blockchain references.

The recorded proof is associated with a MultiversX mainnet transaction. The response can be used to open a public proof page, retrieve a PDF certificate, or consume structured JSON.

Payment can use x402 with USDC on Base without an account, or ACP with EGLD and an API key. The current certification price is served by the live pricing endpoint rather than a fixed value in the documentation.

Setup and configuration

Self-hosting requires Node.js 20 or later, PostgreSQL or Neon, and a MultiversX wallet. The documented setup is to install dependencies, copy .env.example to .env, initialize the database, and start the development process on port 5000.

For API access, the example uses a bearer token in the Authorization header. The API endpoint is hosted at https://provebeforeact.com/api/proof.

Tools and capabilities

The documented integration supports these operations:

• Submit a SHA-256 file hash for certification.
• Include filename, author, and optional webhook metadata in a proof request.
• Receive a proof ID and certification status.
• Retrieve a public proof page, PDF certificate, or machine-readable JSON proof.
• Inspect the associated MultiversX transaction and explorer URL.
• Use x402 or ACP payment paths, subject to their account and currency requirements.

The xProof MCP server should therefore be evaluated against the client’s discovery and authentication behavior before deployment.

Limitations and notes

Hashing is client-side, so the service receives the digest and metadata rather than the original file. A proof confirms the submitted hash and its blockchain record; it does not independently establish that the file’s contents are accurate or safe.

MX-8004 support is optional and the documented production status is not_configured. Do not rely on MX-8004 identity or reputation data unless the status endpoint reports that the integration is active. Historical xproof identifiers remain for compatibility and should not be treated as separate product branding or current performance metrics.