# hashproof [Health: Active]

**Category:** 🔑 Cryptography  
**Repository:** https://github.com/csacanam/hashproof  
**GitHub Stars:** 1  
**npm Downloads (last month):** 164  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hashproof

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

## Tools
Capabilities this server exposes over MCP:

- **get_template_requirements** — Get the required field keys and layout definition of an existing HashProof template. Free, no auth. Always call this before issuing with a template_slug you didn't create in this session.
- **preview_template** — Render a watermarked preview PDF from an INLINE template definition — free, nothing stored, no payment. Use this to iterate field positions (x, y, width, font_size) until the layout is right, then show the final PDF to the human for approval before issuing. page_width/page_height MUST match the background image's pixel dimensions. The PDF is written to a local file; if you can read PDFs, inspect it and adjust yourself.
- **issue_credential** — Issue a verifiable credential — COSTS $0.10 USDC (x402) or 1 API-key credit per call. Get explicit human approval before calling. Requires HASHPROOF_API_KEY or HASHPROOF_WALLET_PRIVATE_KEY in the MCP server env (if neither is set, the error explains both routes). With an API key the credential issues as the key's own entity: `issuer.slug` must match that entity or the call is rejected, so you cannot issue on behalf of another organization. The body follows the HashProof issueCredential schema: issuer{display_name,slug}, platform{display_name,slug}, holder{full_name}, context{type,title}, credential_type, title, values{...}, and optionally template_slug OR an inline template{...} (send only one). Returns id, verification_url, tx_hash and ipfs_cid. Full reference: https://hashproof.dev/skill.md
- **verify_credential** — Verify an issued credential against three independent sources (database, IPFS, blockchain). Free, no auth. Returns status (active/revoked/expired/not_found), issuer verification and the credential data.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "hashproof": {
    "command": "npx",
    "args": ["-y","hashproof-mcp"]
  }
}
```

## Documentation

## What the hashproof MCP server does

The hashproof MCP server lets AI agents work with HashProof, an API for issuing and verifying verifiable credentials. HashProof stores credential JSON in its database, backs it up to IPFS through Pinata, and registers each credential in the `CredentialRegistry` contract on Celo. Published credentials can also be checked through a public verification URL.

The MCP interface covers four operations: previewing a credential template, issuing a credential, verifying a credential, and retrieving the fields required by a template. Previewing, verification, and template requirements are free API operations. Credential issuance costs $0.10 USDC through x402, unless the caller uses a prepaid API key.

## How it works

The hashproof MCP server is available in two deployment modes. A local instance runs through stdio and can pay for issuance with a funded wallet using x402, or authenticate with an API key. A remote Streamable HTTP instance is hosted at `https://api.hashproof.dev/mcp`; it does not have a wallet, so issuing credentials remotely requires an `Authorization: Bearer <api-key>` header.

For x402 payments, the client signs an off-chain authorization for USDC on Base or Celo. The underlying API also exposes a paid verification-request endpoint, but that operation is not listed among the MCP tools described in the README.

After issuance, the credential is recorded in the backend, pinned to IPFS, and registered on Celo. Verification uses HashProof’s free verification path, which performs the service’s full three-layer verification. The deployed mainnet registry is the Celo `CredentialRegistry` contract at `0x7a1B759A602Aba72a70f99Dffd0a386d7504ce9B`.

## Setup and configuration

For a local installation, add the server to an MCP-capable client with:

```bash
claude mcp add hashproof -- npx -y hashproof-mcp
```

This starts the npm package `hashproof-mcp` through stdio. The local process needs access to whichever payment method the caller selects: a funded wallet for x402 payments or an API key.

For remote use, configure the client with:

```bash
claude mcp add --transport http hashproof https://api.hashproof.dev/mcp
```

The remote endpoint requires an API key for credential issuance because it cannot make x402 payments itself.

## Tools and capabilities

The hashproof MCP server provides these named tools:

- `preview_template`: Creates a free watermarked preview PDF for iterating on a custom layout.
- `issue_credential`: Issues one verifiable credential for $0.10 through x402 or with an API key.
- `verify_credential`: Performs free credential verification.
- `get_template_requirements`: Returns the required fields for a selected template.

Use the preview tool before issuance when an agent needs to inspect or refine a custom layout. Use the requirements tool to determine the input fields before constructing a credential. Verification is available without payment, while issuance requires either x402 payment or the prepaid API-key route.

The hashproof MCP server is separate from HashProof’s agent skill and direct HTTP interface. Agents can also use the skill package or call the API directly with an x402-v2 client, but those are alternative access methods rather than additional MCP tools.

_Full upstream README: https://allmcps.com/mcp/hashproof/readme_