Finance · Local MCP server
Hashproof
Issue verifiable credentials from AI agents for $0.10 via x402. On-chain on Celo, IPFS-pinned.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.csacanam/hashproof- Version
- 0.1.2
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-15
- Updated
- 2026-07-15
- Publisher
- csacanam (GitHub) · 4 servers with pages here
- Repository
- github.com/csacanam/hashproof
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | hashproof-mcp | 0.1.2 | stdio |
How to connect Hashproof
Hashproof runs locally from a Node.js package published to the npm registry: hashproof-mcp version 0.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y hashproof-mcp@0.1.2. It reads these environment variables: HASHPROOF_API_KEY (secret), HASHPROOF_WALLET_PRIVATE_KEY (secret) and HASHPROOF_X402_NETWORK; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"hashproof": {
"command": "npx",
"args": [
"-y",
"hashproof-mcp@0.1.2"
],
"env": {
"HASHPROOF_API_KEY": "<secret>",
"HASHPROOF_WALLET_PRIVATE_KEY": "<secret>",
"HASHPROOF_X402_NETWORK": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from csacanam (GitHub)
| Server | Runs |
|---|---|
| ComprabtcNon-custodial Bitcoin DCA for agent treasuries: approve USDT once, stack WBTC on Celo forever. | Local · stdio |
| LoteroProvably fair on-chain slot machine for AI agents: x402 spins on Base, Chainlink VRF results. | Local · stdio |
| VoultiAccept crypto payments from AI agents: invoices + hosted checkout on 5 chains. No API key. | Local · stdio |
More finance servers
| Server | Runs |
|---|---|
| Harbor Crew Cross-Chain ReportPaid read-only reports for 1–5 EVM addresses across four networks; 0.02 supported stablecoin direct. | Remote · HTTP |
| HarvestRead time entries, projects, clients, tasks and invoices; log and update tracked time. | Remote · HTTP |
| HashMCP server for cryptographic hashing — MD5, SHA-1, SHA-256, SHA-384, SHA-512. | Local · stdio |
| Hash Generator APICryptographic hashing — MD5, SHA1, SHA256, SHA512, bcrypt. x402 micropayment. | Remote · SSE |
| Have It PrintedPrint and mail physical documents in the US via USPS, with quotes, agent payment and tracking. | Remote · HTTP |
| Headless TrackerRead-only MCP server: your AI sees your crypto portfolio, never your keys. Not financial advice. | Local · stdio |
| hekkova.comTPermanent memory layer for AI agents. Mint moments to the Polygon blockchain via MCP. | Remote · HTTP |
| HeliusHelius MCP — deeper Solana wallet/asset data than solscan (helius.dev) | Remote · HTTP |