io.github.Zk-nd3r/zcash-mcp
NPM · @FRONTIERCOMPUTE/ZCASH-MCP · SCANNED SEP 20
Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 114 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 669 tokens (~55/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_shielded" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Zk-nd3r/zcash-mcp server?
io.github.Zk-nd3r/zcash-mcp runs locally as an npm package, launched with npx -y @frontiercompute/zcash-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @frontiercompute/zcash-mcp
claude mcp add zk-nd3r-zcash-mcp -- npx -y @frontiercompute/zcash-mcp
{
"mcpServers": {
"zk-nd3r-zcash-mcp": {
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
]
}
}
} {
"servers": {
"zk-nd3r-zcash-mcp": {
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
]
}
}
} codex mcp add zk-nd3r-zcash-mcp -- npx -y @frontiercompute/zcash-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zk-nd3r-zcash-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@frontiercompute/zcash-mcp"
],
"enabled": true
}
}
} openclaw mcp add zk-nd3r-zcash-mcp --command npx --arg -y --arg @frontiercompute/zcash-mcp
mcp_servers:
zk-nd3r-zcash-mcp:
command: "npx"
args: ["-y", "@frontiercompute/zcash-mcp"] {
"McpServers": {
"zk-nd3r-zcash-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@frontiercompute/zcash-mcp"
]
}
}
} assistant mcp add zk-nd3r-zcash-mcp -t stdio -c npx -a -y @frontiercompute/zcash-mcp
{
"mcpServers": {
"zk-nd3r-zcash-mcp": {
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@frontiercompute/zcash-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attest_event ~178
Create a ZAP1 attestation event on Zcash. Writes a typed lifecycle, governance, or agent event to the Merkle tree. Returns leaf hash for verification.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | – | Action type for AGENT_ACTION events |
| api_key | string | – | ZAP1 API key (or set ZAP1_API_KEY env var) |
| event_type | string | yes | Event type: DEPLOYMENT, CONTRACT_ANCHOR, AGENT_ACTION, GOVERNANCE_PROPOSAL, etc. |
| input_hash | string | – | SHA-256 of action input |
| output_hash | string | – | SHA-256 of action output |
| proposal_id | string | – | Proposal ID for governance events |
| serial_number | string | – | Serial number or version tag |
| wallet_hash | string | yes | Wallet hash or agent identifier |
No output schema declared.
No examples provided.
decode_memo ~59
Decode a Zcash shielded memo field. Handles ZAP1 typed memos, ZIP 302, plain text, and raw binary.
| Name | Type | Req | Description |
|---|---|---|---|
| memo | string | yes | Memo data as hex string or base64 (max 1024 bytes decoded) |
No output schema declared.
No examples provided.
get_agent_status ~39
Get attestation summary for a ZAP1 agent: registration, policies, actions, event history.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier |
No output schema declared.
No examples provided.
get_anchor_history ~27
Get all ZAP1 Merkle root anchors with Zcash txids and block heights.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_anchor_status ~30
Get current ZAP1 Merkle tree state: root hash, unanchored leaves, anchor recommendation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_balance ~51
Get attestation and anchor status for a wallet hash via ZAP1 API. Returns lifecycle events, leaf count, and verification links.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet_hash | string | yes | Wallet hash or agent ID to look up |
No output schema declared.
No examples provided.
get_block_height ~19
Get the current Zcash chain height from Zebra.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_events ~44
Get recent ZAP1 attestation events. Returns event type, wallet hash, leaf hash, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of events (default 20) |
No output schema declared.
No examples provided.
get_stats ~27
Get ZAP1 protocol stats: total leaves, anchors, type distribution, and tree height.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_transaction ~49
Get raw transaction data by txid from Zebra.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | Transaction ID (64-char hex) |
| verbose | boolean | – | Return decoded JSON instead of raw hex (default true) |
No output schema declared.
No examples provided.
send_shielded ~90
Generate a zcash: payment URI for shielded ZEC. Encodes address, amount, and optional memo into a scannable URI.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Recipient Zcash shielded address |
| amount | number | yes | Amount in ZEC |
| label | string | – | Optional label for the payment |
| memo | string | – | Optional memo text (max 512 bytes) |
No output schema declared.
No examples provided.
verify_proof ~56
Verify a ZAP1 Merkle proof. Checks whether a leaf hash exists in the ZAP1 attestation tree and returns the proof path.
| Name | Type | Req | Description |
|---|---|---|---|
| leaf_hash | string | yes | Hex-encoded leaf hash to verify (64 chars) |
No output schema declared.
No examples provided.
What is the io.github.Zk-nd3r/zcash-mcp server?
io.github.Zk-nd3r/zcash-mcp is listed in the public MCP registry as io.github.Zk-nd3r/zcash-mcp. Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification. This page covers its npm package (@frontiercompute/zcash-mcp).
Is the io.github.Zk-nd3r/zcash-mcp server safe to use?
io.github.Zk-nd3r/zcash-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Zk-nd3r/zcash-mcp server expose?
io.github.Zk-nd3r/zcash-mcp exposes 12 tools: get_balance, send_shielded, decode_memo, attest_event, verify_proof, and 7 more. Their descriptions and schemas cost roughly 669 tokens of context every time the server is loaded.
Is the io.github.Zk-nd3r/zcash-mcp server still maintained?
io.github.Zk-nd3r/zcash-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Zk-nd3r/zcash-mcp server under?
io.github.Zk-nd3r/zcash-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.