Developer Tools

hashproof.dev

Provides APIs for creating, previewing, issuing, and verifying verifiable credentials via templates with blockchain/IPFS verification.

x402 supported1 endpoint4 known toolsFirst detected August 6, 2026Last detected September 6, 2026

ENDPOINT 1

https://api.hashproof.dev/mcp

No auth detected

MCP server metadata

Name: hashproof
Version: 0.1.3

Capabilities

tools.listChanged

Server instructions

HashProof issues verifiable credentials: each one is registered on Celo, pinned to IPFS, and gets a public verification URL plus a PDF with a QR code. Settle three things with your human before composing an issuance body: 1. How they pay. This remote server has no wallet, so issuing here needs a HashProof API key sent as `Authorization: Bearer <key>` in your MCP client's HTTP headers. To pay $0.10 USDC per credential from their own wallet instead, they use the stdio server (`npx -y hashproof-mcp`), which is a different install — you cannot switch to it from here. For prepaid credits without crypto, hi@hashproof.dev issues a key. 2. Who the issuer is. `issuer` is the organization granting the credential, `platform` is the system managing the issuance; set both to the same organization when there is no third party in between. An API key always issues as its own entity: `issuer.slug` must match that entity or the call is rejected. Issuing in the name of another organization is not something a key or an extra field unlocks — say so plainly instead of looking for a way around it. 3. Whether they want their own design. The default template needs no setup. For a custom one, iterate field positions with `preview_template` (free, nothing stored) and show the final PDF for approval before issuing. Backgrounds must already be hosted at a public image URL — there is no upload endpoint. Issuing costs money and writes to a blockchain: get explicit approval for the final body first. A credential can be revoked afterwards, never edited. Issuer names are self-asserted metadata. Verification reports `issuer_verification_level` — `verified` only when the issuing entity itself is verified, `none` otherwise. The contents are always tamper-evident; the issuer's identity is only as good as that level. Full reference: https://hashproof.dev/skill.md

Known tools 4

get_template_requirements

Get the required field keys and layout definition of an existing HashProof template.

Inferred read-only

preview_template

Render a watermarked preview PDF from an INLINE template definition — free, nothing stored, no payment.

Potential side effects

issue_credential

Issue a verifiable credential — COSTS 1 API-key credit per call.

Inferred read-only

verify_credential

Verify an issued credential against three independent sources (database, IPFS, blockchain).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.hashproof]
url = "https://api.hashproof.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "hashproof": {
      "type": "http",
      "url": "https://api.hashproof.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: hashproof
Remote MCP URL: https://api.hashproof.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "hashproof": {
      "url": "https://api.hashproof.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "hashproof": {
      "type": "http",
      "url": "https://api.hashproof.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "hashproof",
  "transport": "streamable-http",
  "url": "https://api.hashproof.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for hashproof.dev was fetched 2026-08-24T10:19:10.355Z.

Trust status Trusted

hashproof.dev is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.