xProof

Server Details

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

Status: Healthy
Last Tested: 2026-03-12 23:30
Transport: Streamable HTTP
URL
Repository: jasonxkensei/xProof
GitHub Stars: 1

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

7 tools

audit_agent_sessionInspect

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. Schema: https://xproof.app/.well-known/agent-audit-schema.json

ParametersJSON Schema

Name	Required	Description
`context`	No	Optional additional context (model version, environment, tool chain, etc.)
`agent_id`	Yes	Identifier of the agent making the decision
`decision`	Yes	Agent's decision about whether to proceed
`timestamp`	Yes	ISO 8601 timestamp of when the decision was made
`risk_level`	Yes	Assessed risk level of the action
`session_id`	Yes	Unique session identifier (UUID or timestamp-based)
`action_type`	Yes	Category of the action being certified
`inputs_hash`	Yes	SHA-256 of all inputs analyzed before making the decision
`risk_summary`	No	Optional brief risk analysis justifying the decision
`action_description`	Yes	Human-readable description of the specific action

certify_fileInspect

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

ParametersJSON Schema

Name	Required	Description
`filename`	Yes	Original filename with extension
`file_hash`	Yes	SHA-256 hash of the file (64 hex characters)
`author_name`	No	Name of the certifier (default: AI Agent)
`webhook_url`	No	Optional HTTPS URL for on-chain confirmation callback

check_attestationsInspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`wallet`	Yes	MultiversX wallet address (erd1...) of the agent to check

discover_servicesInspect

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

ParametersJSON Schema

Name	Required	Description	Default
No parameters

get_proofInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	Output format: json or md	json
`proof_id`	Yes	UUID of the certification

investigate_proofInspect

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.05 USDC on Base via X-PAYMENT header) or API key authentication. Without payment, returns payment requirements with USDC address and amount.

ParametersJSON Schema

Name	Required	Description	Default
`wallet`	Yes	Agent wallet address (erd1...) that owns the proof
`proof_id`	Yes	UUID of any proof in the action pair — WHY (reasoning), WHAT (action), or heartbeat session proof

verify_proofInspect

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

ParametersJSON Schema

Name	Required	Description	Default
`proof_id`	Yes	UUID of the certification to verify

To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.

Server Details

Available Tools

Discussions

Your Connectors

Resources