Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification.
{
"mcpServers": {
"io-github-zk-nd3r-zcash-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for io.github.Zk-nd3r/zcash-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Zcash MCP server. Connects AI agents to shielded Zcash operations. First privacy chain on the MCP registry.
MCP (Model Context Protocol) is the standard way for AI models to call external tools. This server exposes 18 Zcash tools that any MCP client can use - Claude Desktop, ChatGPT, OpenClaw, or anything that speaks the protocol.
| Tool | What it does |
|------|-------------|
| get_balance | ZAP1 attestation history and anchor status for a wallet hash |
| send_shielded | Generate a zcash: payment URI (ZIP 321) |
| decode_memo | Decode shielded memos - ZAP1 typed, ZIP 302, text, binary |
| attest_event | Write a ZAP1 attestation to the Zcash blockchain |
| verify_proof | Verify a ZAP1 Merkle proof |
| get_stats | ZAP1 protocol stats (leaves, anchors, types) |
| get_block_height | Current chain height from Zebra |
| lookup_transaction | Raw transaction data by txid |
| get_anchor_history | All ZAP1 Merkle root anchors with txids and block heights |
| get_anchor_status | Current Merkle tree state: root, unanchored leaves, recommendation |
| get_events | Recent ZAP1 attestation events with type, wallet hash, leaf hash |
| get_agent_status | Attestation summary for a ZAP1 agent ID |
| zcash_create_invoice | Create a ZAP1 payment invoice, returns address, amount, zcash: URI, expiry |
| zcash_watch_payment | Poll an invoice until paid or timeout, returns txid, height, amount |
| zcash_prove_payment | Fetch the full Merkle proof bundle for a leaf hash |
| zcash_identity_register | Register an agent identity via AGENT_REGISTER attestation |
| zcash_reputation_score | Fetch agent bond data and policy compliance as a reputation object |
| zcash_crosschain_swap | Cross-chain swap intent: ZEC transparent to BTC, USDC, USDT via Ika or NEAR |
| zcash_create_wallet | Create a split-key wallet via Ika 2PC-MPC (secp256k1 signs for ZEC, BTC, ETH) |
| zcash_sign_mpc | Sign a message hash through Ika 2PC-MPC (neither party sees the full key) |
| zcash_shield | Move ZEC from transparent MPC custody to shielded Orchard pool |
| zcash_verify_evm | Verify a ZAP1 Merkle proof on-chain via EVM contract (Sepolia, Base, Arbitrum) |
npx @frontiercompute/zcash-mcp
Or install globally:
npm install -g @frontiercompute/zcash-mcp
Environment variables:
| Variable | Default | Description |
|----------|---------|-------------|
| ZEBRA_RPC_URL | http://127.0.0.1:8232 | Zebra node JSON-RPC endpoint |
| ZAP1_API_URL | https://pay.frontiercompute.io | ZAP1 attestation API |
| ZAP1_API_KEY | none | API key for attest_event |
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 the zcash-mcp binary.
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:
npm run test:offline
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