Zcash MCP Server

@frontiercompute/zcash-mcp npm v1.4.0

Published by @frontiercompute — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

ZAP1 receipts for Zcash agents: verify workflows without trusting the server

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 27

Each tool and what it can reach — statically extracted from the published source.

  • zap1_prove_receiptingests untrusted input
  • attest_eventno sensitive capability
  • decode_memono sensitive capability
  • get_agent_statusno sensitive capability
  • get_anchor_historyno sensitive capability
  • get_anchor_statusno sensitive capability
  • get_block_heightno sensitive capability
  • get_eventsno sensitive capability
  • get_statsno sensitive capability
  • lookup_transactionno sensitive capability
Show 17 more tools ↓
  • verify_proofno sensitive capability
  • zap1_attest_external_actionno sensitive capability
  • zap1_audit_event_logno sensitive capability
  • zap1_check_anchor_freshness_at_heightno sensitive capability
  • zap1_compare_receipt_claimsno sensitive capability
  • zap1_create_receipt_invoiceno sensitive capability
  • zap1_extract_proof_artifactno sensitive capability
  • zap1_verify_evmno sensitive capability
  • zap1_verify_external_receiptno sensitive capability
  • zap1_verify_receipt_chainno sensitive capability
  • zap1_wallet_receipt_requestno sensitive capability
  • zap1_watch_receipt_invoiceno sensitive capability
  • zcash_capability_manifestno sensitive capability
  • zcash_conformance_checkno sensitive capability
  • zcash_identity_registerno sensitive capability
  • zcash_receipt_templateno sensitive capability
  • zcash_reputation_scoreno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.4.0 latest A 96/100 0 1.13.0 2026-09-09

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/frontiercompute-zcash-mcp/badge.svg)](https://mcptrustchecker.com/registry/frontiercompute-zcash-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/frontiercompute-zcash-mcp"><img src="https://mcptrustchecker.com/registry/frontiercompute-zcash-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/frontiercompute-zcash-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @frontiercompute/zcash-mcp --online

Use the free API → How scoring works

More in Developer Tools