English Français العربية

io.github.csacanam/hashproof

Official registry AI and agents

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package hashproof-mcp
Claude Code 
claude mcp add hashproof -e 'HASHPROOF_API_KEY=<your hashproof_api_key>' -e 'HASHPROOF_WALLET_PRIVATE_KEY=<your hashproof_wallet_private_key>' -e 'HASHPROOF_X402_NETWORK=<HASHPROOF_X402_NETWORK>' -- npx -y hashproof-mcp@0.1.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "hashproof": {
            "command": "npx",
            "args": [
                "-y",
                "hashproof-mcp@0.1.2"
            ],
            "env": {
                "HASHPROOF_API_KEY": "<your hashproof_api_key>",
                "HASHPROOF_WALLET_PRIVATE_KEY": "<your hashproof_wallet_private_key>",
                "HASHPROOF_X402_NETWORK": "<HASHPROOF_X402_NETWORK>"
            }
        }
    }
}

Environment variables

  • HASHPROOF_API_KEY secret Prepaid API key (alternative to wallet). One of the two payment methods is required only for issue_credential.
  • HASHPROOF_WALLET_PRIVATE_KEY secret EVM private key of a dedicated wallet holding USDC on Base or Celo — pays $0.10 per issuance via x402.
  • HASHPROOF_X402_NETWORK base (default) or celo

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. HashProof
  2. What it is
  3. Project structure
  4. Deployed contracts
  5. Paid API endpoints
  6. Free endpoints
  7. For AI agents
  8. Quick start

HashProof

Verifiable credentials with IPFS backup, on-chain registry, and pay-per-call API via x402.

What it is

HashProof is a credential issuance API. Organizations and Individuals (entities) issue verifiable credentials to people. Each credential is:

  • Stored as a JSON in the database and backed up on IPFS (Pinata)
  • Registered on-chain in the CredentialRegistry contract on Celo
  • Verifiable via a public URL: https://hashproof.dev/verify/:id

Two ways to pay: micropayment in USDC via x402 (Base or Celo) — no API keys, no subscriptions — or a prepaid API key for enterprise clients (no crypto needed). AI agents can call the API directly using a funded wallet.

Project structure

backend/       Express API — credential issuance, verification, payments
frontend/      React app — landing page, credential verification, entity pages
contracts/     CredentialRegistry smart contract (Celo)
mcp/           MCP server (hashproof-mcp on npm) — use HashProof from any AI agent
skills/        Agent skill (npx skills add csacanam/hashproof)
docs/          Architecture and flow documentation

Deployed contracts

NetworkContractAddress
Celo mainnetCredentialRegistry0x7a1B759A602Aba72a70f99Dffd0a386d7504ce9B

Paid API endpoints

EndpointPriceDescription
POST /issueCredential$0.10 USDCIssue one verifiable credential
POST /entities/:id/verificationRequests$49 USDCSubmit a verification request

Payment is in USDC on Base or Celo via x402. The client signs an off-chain authorization — no gas required.

Free endpoints

EndpointDescription
GET /verify/:idFull 3-layer verification
GET /templates/:ref/requirementsGet required fields for a template
POST /templates/:ref/previewGenerate a preview PDF with watermark (no cost)
GET /statsOn-chain credential counters

For AI agents

HashProof is fully agent-usable — no account, no human onboarding. Three ways in:

  • MCP server, local or remote (listed on the official MCP registry as io.github.csacanam/hashproof):

    # local (stdio) — pays per credential with your own wallet via x402, or an API key
claude mcp add hashproof -- npx -y hashproof-mcp

# remote (Streamable HTTP) — nothing to install, API key required to issue
claude mcp add --transport http hashproof https://api.hashproof.dev/mcp

    Tools: preview_template (free — iterate custom layouts), issue_credential ($0.10 via x402 or API key), verify_credential and get_template_requirements (free). The remote server has no wallet, so it can't do x402 — it needs Authorization: Bearer <api-key>. See mcp/README.md.

  • Agent skill: npx skills add csacanam/hashproof — or read it at hashproof.dev/skill.md.
  • Plain HTTP + x402: POST /issueCredential returns a 402 challenge any x402-v2 client can pay (USDC on Base or Celo). LLM index: hashproof.dev/llms.txt.

Agent identity metadata (ERC-8004 registration-v1): hashproof.dev/metadata.json.

Quick start

See backend/README.md and frontend/README.md for setup instructions. See docs/README.md for the full documentation index.

Frequently asked questions

What is io.github.csacanam/hashproof?

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

How do I install io.github.csacanam/hashproof?

It runs on your machine. In Claude Code: claude mcp add hashproof -e 'HASHPROOF_API_KEY=<your hashproof_api_key>' -e 'HASHPROOF_WALLET_PRIVATE_KEY=<your hashproof_wallet_private_key>' -e 'HASHPROOF_X402_NETWORK=<HASHPROOF_X402_NETWORK>' -- npx -y hashproof-mcp@0.1.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.csacanam/hashproof need an API key?

Yes. It expects HASHPROOF_API_KEY, HASHPROOF_WALLET_PRIVATE_KEY, which you set in its configuration.

Is io.github.csacanam/hashproof open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.csacanam/hashproof?

It is published by csacanam. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.