io.github.Zk-nd3r/zcash-mcp

MCPcommunity
v0.2.2io.github.Zk-nd3rUnknownUpdated 3mo agonpmGitHub

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

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 Core rule: observe state, bound the claim, hash evidence, issue a receipt, MCP is the standard way for AI agents to call…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.Zk-nd3r
LicenseUnknown
Version0.2.2
Sourcemcp-registry
npm@frontiercompute/zcash-mcp
GitHubFrontier-Compute/zcash-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface27 tools · none privileged
Security scan✓ Cleanv1.4.0 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

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 Core rule: observe state, bound the claim, hash evidence, issue a receipt, MCP is the standard way for AI agents to call external tools. exposes the ZAP1 attestation layer for agents that need verifiable receipts around Zcash…

Keywords
mcp