About Frontier-Compute/zcash-mcp
Frontier-Compute/zcash-mcp is an MCP server in the Developer Tools category: chain attestation, and proof verification.
Install
git clone https://github.com/Frontier-Compute/zcash-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (28)
attest_eventCreate a typed ZAP1 attestation leaf for later anchoring
Parameters not published.
decode_memoDecode Zcash memo payloads: ZAP1 typed, ZIP 302, text, binary
Parameters not published.
get_agent_statusAttestation summary for a ZAP1 agent ID
Parameters not published.
get_anchor_historyAll ZAP1 Merkle root anchors with txids and block heights
Parameters not published.
get_anchor_statusCurrent Merkle tree state: root, unanchored leaves, recommendation
Parameters not published.
get_block_heightCurrent chain height from Zebra
Parameters not published.
get_eventsRecent ZAP1 attestation events with type, wallet hash, leaf hash
Parameters not published.
get_statsZAP1 protocol stats: leaves, anchors, types
Parameters not published.
lookup_transactionRaw transaction data by txid
Parameters not published.
verify_proofVerify a ZAP1 Merkle proof
Parameters not published.
Show all 28 tools
zap1_attest_external_actionMap bounded external verification evidence into the supported ZAP1 `AGENT_ACTION` write contract and precompute the expected typed leaf
Parameters not published.
zap1_audit_event_logReplay a receipt sequence against a caller-supplied event-type policy
Parameters not published.
zap1_check_anchor_freshness_at_heightCompute depth arithmetic from supplied heights without claiming chain confirmation
Parameters not published.
zap1_compare_receipt_claimsCompare two ZAP1 receipts for claim, evidence, event, and anchor divergence
Parameters not published.
zap1_create_receipt_invoiceCreate ZAP1 receipt metadata for an external payment workflow
Parameters not published.
zap1_extract_proof_artifactExtract the portable proof artifact from a ZAP1 receipt
Parameters not published.
zap1_prove_receiptFetch the full Merkle proof bundle for a leaf hash
Parameters not published.
zap1_verify_evmVerify a ZAP1 Merkle proof on-chain via EVM contract
Parameters not published.
zap1_verify_external_receiptValidate legacy v1 external-receipt shape without claiming cryptographic inclusion or anchor confirmation
Parameters not published.
zap1_verify_receipt_chainValidate legacy v1 receipt-sequence shape without claiming proof or anchor validity
Parameters not published.
zap1_verify_receipt_v2Verify the official proof-bundle-v2 plus retained `AGENT_ACTION` witness, or an integration receipt-v2; anchor confirmation remains separate
Parameters not published.
zap1_wallet_receipt_requestConvert a wallet-layer action result into hash-only ZAP1 receipt request fields
Parameters not published.
zap1_watch_receipt_invoicePoll receipt-invoice status until paid or timeout
Parameters not published.
zcash_capability_manifestMachine-readable scope map for agent use: covered surfaces, excluded wallet functions, and composition rules
Parameters not published.
zcash_conformance_checkValidate only the shape of a frozen v1 receipt packet; v1 cannot prove inclusion or anchor confirmation
Parameters not published.
zcash_identity_registerRegister an agent identity via AGENT_REGISTER attestation
Parameters not published.
zcash_receipt_templateCustomer-ready receipt workflow for agent actions, payment receipts, operator lifecycle events, and policy attestations
Parameters not published.
zcash_reputation_scoreFetch agent bond data and policy compliance as a reputation object
Parameters not published.
Ask AI
Ask AI about Frontier-Compute/zcash-mcp
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
zcash-mcp
Zcash MCP server. Connects AI agents to shielded Zcash operations. Published on the MCP registry.
MCP (Model Context Protocol) is the standard way for AI models to call external tools. This server exposes 12 Zcash tools that any MCP client can use - Claude Desktop, ChatGPT, OpenClaw, or anything that speaks the protocol.
Tools
| 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) |
Install
npx @frontiercompute/zcash-mcp
Or install globally:
npm install -g @frontiercompute/zcash-mcp
Configuration
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 |
Claude Desktop
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"
}
}
}
}
Any MCP client
The server communicates over stdio using JSON-RPC. Point your MCP client at the zcash-mcp binary.
Build from source
git clone https://github.com/Frontier-Compute/zcash-mcp.git
cd zcash-mcp
npm ci
npm run build
node dist/index.js
Testing
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
test:live drives the MCP server over stdio and exercises the live tool surface, not just the underlying HTTP endpoints. Set ZAP1_AGENT_ID if you want the get_agent_status check to target a specific deployed agent.
GitHub Actions mirrors that split:
.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.
Dependencies
- A running Zebra node for chain queries (get_block_height, lookup_transaction)
- The ZAP1 API at pay.frontiercompute.io for attestation tools (get_balance, attest_event, verify_proof, get_stats, get_anchor_history, get_anchor_status, get_events, get_agent_status)
- Memo decoding works locally with no external dependencies
Related Packages
| Package | What it does |
|---|---|
| @frontiercompute/zcash-ika | Zcash + Bitcoin signing via Ika 2PC-MPC |
| @frontiercompute/openclaw-zap1 | OpenClaw skill for ZAP1 attestation |
| @frontiercompute/zap1 | ZAP1 attestation client |
| @frontiercompute/silo-zap1 | Silo agent attestation via ZAP1 |
Links
- Dashboard - live ZAP1 attestation dashboard
- MCP Registry - published MCP server listing
- Frontier Compute - project homepage
License
MIT
quickstart (5 minutes)
add to your MCP config:
{
"mcpServers": {
"zcash": {
"command": "npx",
"args": ["@frontiercompute/zcash-mcp"]
}
}
}
restart your client. ask: "what is the current zcash block height?"
done. 22 tools available. no API key needed for read operations.
get a trial key for write operations:
curl -s -X POST https://frontiercompute.cash/api/trial-key
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.