World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Zcash shielded operations for AI agents. Memo decoding, attestation, proof verification.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 2/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Zcash MCP. Follow https://mcp.popnx.com/i/zk-nd3r-zcash-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Zcash MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "zcash": { "command": "npx", "args": [ "-y", "@frontiercompute/zcash-mcp" ], "env": { "ZAP1_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ZAP1_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Zcash MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
SettingsDeveloperEdit Config
{
"mcpServers": {
"zcash": {
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
],
"env": {
"ZAP1_API_KEY": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Zcash MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Zcash MCP or shows a Zcash MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Zcash MCP yet
Zcash MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Zcash MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Zcash MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Zcash MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user zcash --env ZAP1_API_KEY=your-value -- npx -y @frontiercompute/zcash-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ZAP1_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Zcash MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user zcash --env ZAP1_API_KEY=your-value -- npx -y @frontiercompute/zcash-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Zcash MCP listed as connected
Use Zcash MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Zcash MCP or shows a Zcash MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Zcash MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Zcash MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "zcash": { "command": "npx", "args": [ "-y", "@frontiercompute/zcash-mcp" ], "env": { "ZAP1_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ZAP1_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Zcash MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
In the Zcash MCP settings, ZAP1_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Zcash MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Zcash MCP or shows a Zcash MCP tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Zcash MCP key (create it on the maker’s site) · Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Zcash MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "zcash": { "type": "stdio", "command": "npx", "args": [ "-y", "@frontiercompute/zcash-mcp" ], "env": { "ZAP1_API_KEY": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For ZAP1_API_KEY, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Zcash MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
In the Zcash MCP settings, ZAP1_API_KEY is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Zcash MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Zcash MCP or shows a Zcash MCP tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user zcash --env ZAP1_API_KEY=your-value -- npx -y @frontiercompute/zcash-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"zcash": {
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
],
"env": {
"ZAP1_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"zcash": {
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
],
"env": {
"ZAP1_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"zcash": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@frontiercompute/zcash-mcp"
],
"env": {
"ZAP1_API_KEY": "your-value"
}
}
}
}ZAP1_API_KEY secret required envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: @frontiercompute/zcash-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The publisher (Zk-nd3r) is not the repo owner (Frontier-Compute); someone else may have listed it
Code last changed 3 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @frontiercompute/zcash-mcp@0.2.2
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/zk-nd3r-zcash-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ZAP1_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 months ago, and the latest version (0.2.2) reached the registry 8 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Zcash MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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:
attest: create a typed event leaf.anchor: commit leaves into a Merkle root anchored to Zcash.prove: return a receipt packet for a leaf.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:
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.
The zcash_capability_manifest tool gives agents a machine-readable scope map:
Good fits:
Poor fits:
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 hashespayment_receipt: bind invoice or payment metadata to a ZAP1 leaf and later prove inclusion under an anchored rootoperator_lifecycle: record deployment, upgrade, incident, recovery, or policy state as a verifiable lifecycle eventpolicy_attestation: record an agent, service, or workflow policy decision as a verifiable eventExpected flow:
zcash_capability_manifest to confirm the attestation boundary.zcash_receipt_template for the use case.zap1_wallet_receipt_request to convert the wallet result into hash-only attest_event arguments.attest_event to create the typed ZAP1 leaf.get_anchor_status to check whether the leaf is anchored or waiting.verify_proof to verify tree inclusion.zap1_prove_receipt to fetch a handoff proof bundle.Acceptance checks:
leaf_countRed-team rejects:
ZAP1 verifies ZAP1 receipts. It does not audit or guarantee any external wallet, route, payment, bridge, exchange, or settlement system referenced by a receipt.
| Tool | What it does |
|---|---|
zcash_capability_manifest | Machine-readable scope map for agent use: covered surfaces, excluded wallet functions, and composition rules |
zcash_conformance_check | Validate only the shape of a frozen v1 receipt packet; v1 cannot prove inclusion or anchor confirmation |
zcash_receipt_template | Customer-ready receipt workflow for agent actions, payment receipts, operator lifecycle events, and policy attestations |
zap1_wallet_receipt_request | Convert a wallet-layer action result into hash-only ZAP1 receipt request fields |
zap1_attest_external_action | Map bounded external verification evidence into the supported ZAP1 AGENT_ACTION write contract and precompute the expected typed leaf |
zap1_verify_external_receipt | Validate legacy v1 external-receipt shape without claiming cryptographic inclusion or anchor confirmation |
zap1_verify_receipt_v2 | Verify the official proof-bundle-v2 plus retained AGENT_ACTION witness, or an integration receipt-v2; anchor confirmation remains separate |
zap1_extract_proof_artifact | Extract the portable proof artifact from a ZAP1 receipt |
zap1_check_anchor_freshness_at_height | Compute depth arithmetic from supplied heights without claiming chain confirmation |
zap1_verify_receipt_chain | Validate legacy v1 receipt-sequence shape without claiming proof or anchor validity |
zap1_compare_receipt_claims | Compare two ZAP1 receipts for claim, evidence, event, and anchor divergence |
zap1_audit_event_log | Replay a receipt sequence against a caller-supplied event-type policy |
attest_event | Create a typed ZAP1 attestation leaf for later anchoring |
verify_proof | Verify a ZAP1 Merkle proof |
zap1_prove_receipt | Fetch the full Merkle proof bundle for a leaf hash |
get_anchor_history | All ZAP1 Merkle root anchors with txids and block heights |
get_anchor_status | Current Merkle tree state: root, unanchored leaves, recommendation |
get_stats | ZAP1 protocol stats: leaves, anchors, types |
get_events | Recent ZAP1 attestation events with type, wallet hash, leaf hash |
get_agent_status | Attestation summary for a ZAP1 agent ID |
zcash_identity_register | Register an agent identity via AGENT_REGISTER attestation |
zcash_reputation_score | Fetch agent bond data and policy compliance as a reputation object |
decode_memo | Decode Zcash memo payloads: ZAP1 typed, ZIP 302, text, binary |
zap1_create_receipt_invoice | Create ZAP1 receipt metadata for an external payment workflow |
zap1_watch_receipt_invoice | Poll receipt-invoice status until paid or timeout |
get_block_height | Current chain height from Zebra |
lookup_transaction | Raw transaction data by txid |
zap1_verify_evm | Verify a ZAP1 Merkle proof on-chain via EVM contract |
npx @frontiercompute/zcash-mcp
Or install globally:
npm install -g @frontiercompute/zcash-mcp
Add this to your MCP config:
{
"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:
curl -s -X POST https://api.frontiercompute.cash/trial-key
Environment variables:
| Variable | Default | Description |
|---|---|---|
ZEBRA_RPC_URL | http://127.0.0.1:8232 | Zebra node JSON-RPC endpoint |
ZAP1_API_URL | https://api.frontiercompute.cash | ZAP1 attestation API |
ZAP1_API_KEY | none | API key for write operations |
Add to ~/Library/Application Support/Claude/claude_desktop_config.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" } } } }
The server communicates over stdio using JSON-RPC. Point your MCP client at the zcash-mcp binary.
git clone https://github.com/Frontier-Compute/zcash-mcp.git
cd zcash-mcp npm ci npm run build node dist/index.js
Offline verification covers the built stdio server and a clean-room install from the packed npm tarball:
npm run test:offline
Live verification hits a real Zebra RPC and ZAP1 API:
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.| Package | What it does |
|---|---|
| @frontiercompute/zcash-ika | Zcash and Bitcoin signing via Ika 2PC-MPC |
| @frontiercompute/openclaw-zap1 | OpenClaw skill for ZAP1 attestation |
| [@frontiercompute/zap1](https://www.npmjs.com/package/@frontierc