Zcash Mcp

io.github.Zk-nd3r由 GitHub 账号 Zk-nd3r 发布v0.2.2更新于 Oct 24, 2026

Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification.

概览

AI 生成的概览

面向 Zcash 智能体工作流的 ZAP1 存证与证明回执层:创建存证叶子、查询锚定状态、验证 Merkle 证明并解码备注。

可以做什么
  • 创建与查看存证回执:生成类型化叶子、获取证明包、比较回执声明、审计事件日志
  • 验证证明:校验 Merkle 包含关系、v2 回执包、外部回执以及 EVM 链上验证
  • 查询锚定与链上状态:锚定历史与状态、协议统计、近期事件、智能体状态、区块高度、交易查询
  • 搭建集成:能力清单、回执模板、钱包操作回执请求、外部操作存证、回执发票
  • 在本地解码 Zcash 备注内容(ZAP1 类型化、ZIP 302、文本、二进制)
适用场景
当智能体需要为某个 Zcash 相关操作留下可验证回执(如智能体操作、支付或发票证明、运维生命周期事件、策略存证、跨智能体交接),且对方日后要在不信任原始智能体的前提下自行验证时使用。它补充而非替代钱包。
运行要求
通过 npx 从 npm 包以 stdio 在本地运行。链上查询需要运行中的 Zebra 节点(ZEBRA_RPC_URL,默认本地端点),存证、证明、锚定、事件与回执工具需要 ZAP1 API(ZAP1_API_URL)。写操作需在 ZAP1_API_KEY 中提供 API 密钥;只读工具无需密钥。备注解码可离线完成。
安装前请注意
写操作需要 ZAP1_API_KEY 密钥,并会发送给 ZAP1 API;只读工具不需要密钥。存证、发票与身份类工具会向该第三方服务写入数据,回执发票涉及支付流程。它不是钱包:不保管密钥、不扫描余额、不签名或广播交易,回执也不审计或担保其引用的外部系统。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Zcash Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

zcash-mcp

[npm] [MCP Registry] [downloads] [license]

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-mcp exposes 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.

Why ZAP1

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:

  1. attest: create a typed event leaf.
  2. anchor: commit leaves into a Merkle root anchored to Zcash.
  3. prove: return a receipt packet for a leaf.
  4. 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.

See ZAP1 Proof Rail for the category boundary, receipt model, integration pattern, and red-team rejects. See ZAP1 Conformance for the receipt contract agents and integrations should satisfy. See Wallet Receipt Integration for the wallet-action handoff pattern. See External Rail Receipts for generic external-action receipt requests, and Receipt Disclosure Profiles for public, counterparty, auditor, grant, compliance, and internal packet shapes.

Capability Boundary

The zcash_capability_manifest tool 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

Good fits:

  • 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

Poor fits:

  • holding keys
  • scanning wallet balances
  • signing PCZTs
  • broadcasting shielded spends
  • replacing a wallet SDK

Customer Flow

Use zcash_receipt_template first 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

Expected flow:

  1. Call zcash_capability_manifest to confirm the attestation boundary.
  2. Call zcash_receipt_template for the use case.
  3. For wallet actions, call zap1_wallet_receipt_request to convert the wallet result into hash-only attest_event arguments.
  4. Call attest_event to create the typed ZAP1 leaf.
  5. Call get_anchor_status to check whether the leaf is anchored or waiting.
  6. Call verify_proof to verify tree inclusion.
  7. Call zap1_prove_receipt to fetch a handoff proof bundle.

Acceptance checks:

  • the receipt has a leaf hash
  • the leaf verifies under a returned Merkle root
  • v2 receipts retain every sibling position and the committed leaf_count
  • anchor finality comes from a separately verified root-opening artifact, not txid, height, or status metadata alone
  • another verifier can repeat verification without trusting the original agent
  • no private keys, seeds, PCZTs, or wallet scan state were sent to this server

Red-team rejects:

  • 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.

Tools

ToolWhat it does
zcash_capability_manifestMachine-readable scope map for agent use: covered surfaces, excluded wallet functions, and composition rules
zcash_conformance_checkValidate only the shape of a frozen v1 receipt packet; v1 cannot prove inclusion or anchor confirmation
zcash_receipt_templateCustomer-ready receipt workflow for agent actions, payment receipts, operator lifecycle events, and policy attestations
zap1_wallet_receipt_requestConvert a wallet-layer action result into hash-only ZAP1 receipt request fields
zap1_attest_external_actionMap bounded external verification evidence into the supported ZAP1 AGENT_ACTION write contract and precompute the expected typed leaf
zap1_verify_external_receiptValidate legacy v1 external-receipt shape without claiming cryptographic inclusion or anchor confirmation
zap1_verify_receipt_v2Verify the official proof-bundle-v2 plus retained AGENT_ACTION witness, or an integration receipt-v2; anchor confirmation remains separate
zap1_extract_proof_artifactExtract the portable proof artifact from a ZAP1 receipt
zap1_check_anchor_freshness_at_heightCompute depth arithmetic from supplied heights without claiming chain confirmation
zap1_verify_receipt_chainValidate legacy v1 receipt-sequence shape without claiming proof or anchor validity
zap1_compare_receipt_claimsCompare two ZAP1 receipts for claim, evidence, event, and anchor divergence
zap1_audit_event_logReplay a receipt sequence against a caller-supplied event-type policy
attest_eventCreate a typed ZAP1 attestation leaf for later anchoring
verify_proofVerify a ZAP1 Merkle proof
zap1_prove_receiptFetch the full Merkle proof bundle for a leaf hash
get_anchor_historyAll ZAP1 Merkle root anchors with txids and block heights
get_anchor_statusCurrent Merkle tree state: root, unanchored leaves, recommendation
get_statsZAP1 protocol stats: leaves, anchors, types
get_eventsRecent ZAP1 attestation events with type, wallet hash, leaf hash
get_agent_statusAttestation summary for a ZAP1 agent ID
zcash_identity_registerRegister an agent identity via AGENT_REGISTER attestation
zcash_reputation_scoreFetch agent bond data and policy compliance as a reputation object
decode_memoDecode Zcash memo payloads: ZAP1 typed, ZIP 302, text, binary
zap1_create_receipt_invoiceCreate ZAP1 receipt metadata for an external payment workflow
zap1_watch_receipt_invoicePoll receipt-invoice status until paid or timeout
get_block_heightCurrent chain height from Zebra
lookup_transactionRaw transaction data by txid
zap1_verify_evmVerify a ZAP1 Merkle proof on-chain via EVM contract

Install

bash
npx @frontiercompute/zcash-mcp

Or install globally:

bash
npm install -g @frontiercompute/zcash-mcp

Quickstart

Add this to your MCP config:

json
{  "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.

Get a trial key for write operations:

bash
curl -s -X POST https://api.frontiercompute.cash/trial-key

Configuration

Environment variables:

VariableDefaultDescription
ZEBRA_RPC_URLhttp://127.0.0.1:8232Zebra node JSON-RPC endpoint
ZAP1_API_URLhttps://api.frontiercompute.cashZAP1 attestation API
ZAP1_API_KEYnoneAPI key for write operations

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

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

bash
git clone https://github.com/Frontier-Compute/zcash-mcp.gitcd zcash-mcpnpm cinpm run buildnode dist/index.js

Testing

Offline verification covers the built stdio server and a clean-room install from the packed npm tarball:

bash
npm run test:offline

Live verification hits a real Zebra RPC and ZAP1 API:

bash
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.yml runs deterministic packaging and MCP handshake checks on every push and pull request.
  • .github/workflows/live-e2e.yml runs secret-backed live checks on main, on a schedule, and by manual dispatch.

Dependencies

  • A running Zebra node for chain queries
  • The ZAP1 API for attestation, proof, anchor, event, and receipt tools
  • Memo decoding works locally with no external dependencies

Related Packages

PackageWhat it does
@frontiercompute/zcash-ikaZcash and Bitcoin signing via Ika 2PC-MPC
@frontiercompute/openclaw-zap1OpenClaw skill for ZAP1 attestation
@frontiercompute/zap1ZAP1 attestation client
@frontiercompute/silo-zap1Silo agent attestation via ZAP1

Links

License

MIT

来源:README.md,提交 5e49844

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.2.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分