Zcash MCP
About
MCP server for Zcash with 22 tools for shielded transactions, attestation verification, and wallet management
Details
- Author
- frontier-compute
- Categories
- Other, Finance, Security
Jump to
Setup
Install Zcash MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/frontier-compute/zcash-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
ZAP1 receipts for Zcash agents: verify workflows without trusting the server.
ZAP1 is an attestation and proof rail for Zcash workflows. Frontier Compute maintains the reference ZAP1 implementation.
A wrapper makes you trust the server. ZAP1 makes the server unnecessary to trust.
Core rule: observe state, bound the claim, hash evidence, issue a receipt, verify later.
MCP is the standard way for AI agents to call external tools.zcash-mcpexposes the ZAP1 attestation layer for agents that need verifiable receipts around Zcash workflows: create ZAP1 attestation leaves, query anchor state, and verify proof receipts.
This is not a full wallet MCP. Balance scanning, private key custody, seed handling, PCZT signing, shielded spend construction, and lightwalletd or Zaino wallet synchronization are complementary wallet-layer work, not this server's scope.
Wallet MCPs can move value. ZAP1 proves the workflow around the value, and the counterparty can verify the proof without trusting Frontier.
Tool servers expose what a backend says right now. ZAP1 produces a receipt that another party can verify later from the schema, proof material, and Zcash anchor.
ZAP1 is the proof rail for Zcash agent workflows:
- attest: create a typed event leaf.
- anchor: commit leaves into a Merkle root anchored to Zcash.
- prove: return a receipt packet for a leaf.
- verify: let another party check the receipt without trusting the original agent.
Agent systems need more than a payment or a transaction lookup. They need a receipt that another agent, user, auditor, or service can verify later:
- what event was asserted
- which agent or workflow asserted it
- which ZAP1 leaf records it
- which Merkle root includes it
- which Zcash transaction anchored that root
- how to verify the proof without trusting the original agent
That is the lane for this server. It gives Zcash agents a receipt layer that can sit beside any wallet, signer, custody system, lightwalletd stack, Zaino stack, or application-specific payment flow.
SeeZAP1 Proof Railfor the category boundary, receipt model, integration pattern, and red-team rejects. SeeZAP1 Conformancefor the receipt contract agents and integrations should satisfy. SeeWallet Receipt Integrationfor the wallet-action handoff pattern. SeeExternal Rail Receiptsfor generic external-action receipt requests, andReceipt Disclosure Profilesfor public, counterparty, auditor, grant, compliance, and internal packet shapes.
Thezcash_capability_manifesttool gives agents a machine-readable scope map:
- covered here: ZAP1 receipts, lifecycle attestations, proof verification, anchor state, memo decoding, and public chain context
- excluded here: custody, seed handling, balance scanning, PCZT signing, shielded spend construction, and wallet-server synchronization
- composition rule: use this server before or after wallet-layer actions to create, query, and verify receipts
- agent action receipts
- payment and invoice proof packets
- wallet action receipts
- external action receipts
- operator lifecycle events
- grant proof packets
- compliance audit packets
- policy and reputation attestations
- public anchor verification for private workflows
- cross-agent handoffs where the receiver needs proof, not custody
- holding keys
- scanning wallet balances
- signing PCZTs
- broadcasting shielded spends
- replacing a wallet SDK
Usezcash_receipt_templatefirst when you are wiring ZAP1 into a product. It returns a customer-ready workflow for the receipt type you want:
- agent_action: prove an agent performed a named action with specific input and output hashes
- payment_receipt: bind invoice or payment metadata to a ZAP1 leaf and later prove inclusion under an anchored root
- operator_lifecycle: record deployment, upgrade, incident, recovery, or policy state as a verifiable lifecycle event
- policy_attestation: record an agent, service, or workflow policy decision as a verifiable event
- Callzcash_capability_manifestto confirm the attestation boundary.
- Callzcash_receipt_templatefor the use case.
- For wallet actions, callzap1_wallet_receipt_requestto convert the wallet result into hash-onlyattest_eventarguments.
- Callattest_eventto create the typed ZAP1 leaf.
- Callget_anchor_statusto check whether the leaf is anchored or waiting.
- Callverify_proofto verify tree inclusion.
- Callzap1_prove_receiptto fetch a handoff proof bundle.
- the receipt has a leaf hash
- the leaf verifies under a returned Merkle root
- anchored receipts include an anchor transaction or anchor height
- another verifier can repeat verification without trusting the original agent
- no private keys, seeds, PCZTs, or wallet scan state were sent to this server
- treating a payment URI as proof of payment
- treating an unanchored leaf as final settlement evidence
- treating a quote, route, or intent hash as settlement evidence by itself
- asking this server to sign, scan balances, recover seeds, or hold keys
- mixing custody claims into ZAP1 receipt claims
- hiding the distinction between wallet action and receipt verification
ZAP1 verifies ZAP1 receipts. It does not audit or guarantee any external wallet, route, payment, bridge, exchange, or settlement system referenced by a receipt.
npm install -g @frontiercompute/zcash-mcp
{ "mcpServers": { "zcash": { "command": "npx", "args": ["@frontiercompute/zcash-mcp"] } } }
Restart your client and ask for the current Zcash block height. Read-only tools do not need an API key.
curl -s -X POST https://api.frontiercompute.cash/trial-key
Add to~/Library/Application Support/Claude/claude_desktop_config.json:
{ "mcpServers": { "zcash": { "command": "npx", "args": ["@frontiercompute/zcash-mcp"], "env": { "ZEBRA_RPC_URL": "http://127.0.0.1:8232", "ZAP1_API_KEY": "your-key-here" } } } }
The server communicates over stdio using JSON-RPC. Point your MCP client at thezcash-mcpbinary.
git clone https://github.com/Frontier-Compute/zcash-mcp.git cd zcash-mcp npm ci npm run build node dist/index.js
Offline verification covers the built stdio server and a clean-room install from the packed npm tarball:
Live verification hits a real Zebra RPC and ZAP1 API:
ZEBRA_RPC_URL=http://127.0.0.1:8232 \ ZAP1_API_URL=http://127.0.0.1:3080 \ ZAP1_API_KEY=your-key-here \ npm run test:live
test:livedrives the MCP server over stdio and exercises the live tool surface, not just the underlying HTTP endpoints. SetZAP1_AGENT_IDif you want theget_agent_statuscheck to target a specific deployed agent.
- .github/workflows/offline-ci.ymlruns deterministic packaging and MCP handshake checks on every push and pull request.
- .github/workflows/live-e2e.ymlruns secret-backed live checks onmain, on a schedule, and by manual dispatch.
- Dashboard
- MCP Registry
- Frontier Compute
- Live stats
AIN bias & stability scoring engine — 68 tools across finance, gaming, AI, crypto, security. Free 5K tokens/mo.
The Behavioural Prediction MCP Server provides AI-powered tools to analyze wallet behaviour prediction,fraud detection and rug pull prediction.
Provides risk scoring and asset information for blockchain addresses, domains, and dApps using the BICScan API.
Detects potential risks in Solana meme tokens to help avoid rug pulls and unsafe projects.
221 crypto security tools. Scam detection, wallet forensics, whale tracking. 13 chains. The Bloomberg Terminal of Shitcoins.
SelfLabbs Security Intel (x402 pay-per-call)
Pay-per-call MCP: autonomous agents pay in USDC on Base via x402 for keyless CVE and package-vulnerability lookups.
Keyless CEX/DEX signing for AI agents — exchange API keys stay inside an AWS Nitro Enclave, so a prompt-injected agent can't leak them. Binance, OKX, Bybit, KuCoin, Hyperliquid, Asterdex.
MCP to interface with multiple blockchains, staking, DeFi, swap, bridging, wallet management, DCA, Limit Orders, Coin Lookup, Tracking and more.
MCP server for Bitnovo Pay integration with AI agents. Provides cryptocurrency payment capabilities through Bitnovo Pay API. Features include payment creation, status checking, QR code generation, and webhook management with support for multiple tunnel providers (ngrok, zrok, manual).
Financial intelligence for AI agents — 31 tools across 8 data sources including regime, derivatives, stablecoin flows, momentum, macro, weather patterns, and political cycles.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
