Zcash Mcp
Let coding agents decode shielded Zcash memos, verify proofs, and run attestations without hand-rolling Zcash RPC clients.
Overview
Zcash MCP is an MCP server for the Build phase that lets agents perform shielded Zcash memo decoding, attestation, and proof verification via ZAP1-backed tools.
What is this MCP server?
- Shielded Zcash operations tailored for AI agents (memos, attestations, proofs)
- stdio npm package @frontiercompute/zcash-mcp v0.2.2
- ZAP1_API_KEY required for write operations (secret env)
- Memo decoding and proof verification without custom node scripting
- Frontier Compute open-source repo zcash-mcp on GitHub
- Server version 0.2.2 (@frontiercompute/zcash-mcp)
- ZAP1_API_KEY environment variable for writes
- stdio npm transport
What problem does it solve?
Agents cannot safely reason about shielded Zcash memos and proofs when every check requires bespoke RPC scripts and key handling.
Who is it for?
Builders adding Zcash shielded flows to agents or backends who already use ZAP1 and want stdio MCP tooling.
Skip if: Founders on Stripe-only checkout, teams without Zcash literacy, or anyone avoiding secret API keys in local dev.
What do I get? / Deliverables
Your agent gains typed MCP tools for shielded reads and verified writes so privacy payment logic stays in the integration layer you control.
- Agent-callable shielded memo decode and attestation flows
- Proof verification steps usable in build and ship checklists
- Integration surface for ZAP1-backed writes from your codebase
Recommended MCP Servers
Journey fit
Shielded payment and attestation hooks belong in Build when you wire privacy-preserving money flows into a product or agent backend. Integrations is the right shelf for an npm MCP that bridges ZAP1 and Zcash semantics into agent tool calls.
How it compares
Finance and cryptography MCP integration, not a general ledger skill or a consumer wallet app.
Common Questions / FAQ
Who is Zcash MCP for?
Developers and solo builders wiring shielded Zcash into AI agents or APIs who need memo and proof tooling instead of manual node calls.
When should I use Zcash MCP?
During Build integrations when your product must decode shielded memos, verify proofs, or submit attestations through ZAP1.
How do I add Zcash MCP to my agent?
Install @frontiercompute/zcash-mcp, configure stdio MCP in your agent, and set ZAP1_API_KEY for any write operations.