Frontier-Compute/zcash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZAP1_API_KEY | No | API key for attest_event | |
| ZAP1_API_URL | No | ZAP1 attestation API | https://pay.frontiercompute.io |
| ZEBRA_RPC_URL | No | Zebra node JSON-RPC endpoint | http://127.0.0.1:8232 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decode_memoA | Decode a Zcash shielded memo field. Handles ZAP1 typed memos, ZIP 302, plain text, and raw binary. |
| attest_eventB | Create a typed ZAP1 attestation event leaf for later anchoring. Returns a leaf hash for verification. |
| verify_proofA | Verify a ZAP1 Merkle proof. Checks whether a leaf hash exists in the ZAP1 attestation tree and returns the proof path. |
| get_statsA | Get ZAP1 protocol stats: total leaves, anchors, type distribution, and tree height. |
| get_block_heightA | Get the current Zcash chain height from Zebra. |
| lookup_transactionA | Get raw transaction data by txid from Zebra. |
| get_anchor_historyA | Get all ZAP1 Merkle root anchors with Zcash txids and block heights. |
| get_anchor_statusA | Get current ZAP1 Merkle tree state: root hash, unanchored leaves, anchor recommendation. |
| get_eventsC | Get recent ZAP1 attestation events. Returns event type, wallet hash, leaf hash, and timestamps. |
| get_agent_statusA | Get attestation summary for a ZAP1 agent: registration, policies, actions, event history. |
| zap1_create_receipt_invoiceA | Create ZAP1 receipt metadata for an external payment workflow. Returns invoice metadata for later receipt verification; this server does not sign, scan, or broadcast. |
| zap1_watch_receipt_invoiceA | Poll ZAP1 receipt-invoice status until paid or timeout. Returns public receipt status only; this server does not scan wallet state. |
| zap1_prove_receiptA | Fetch a ZAP1 Merkle proof bundle for a leaf hash. Returns the full proof: leaf, path, root, and anchor. |
| zcash_identity_registerB | Register an agent identity on ZAP1 via an AGENT_REGISTER attestation. Returns the leaf hash and verification URLs for the registration event. |
| zcash_reputation_scoreB | Fetch an agent's reputation from ZAP1. Combines bond data and policy compliance into a single object: attestation count, violations, bonds, and compliant flag. |
| zap1_verify_evmB | Verify a ZAP1 Merkle proof on-chain via the EVM ZAP1Verifier contract. Checks that a leaf hash is included in a registered Zcash anchor root. Supports Sepolia (testnet), Base, and Arbitrum. |
| zcash_capability_manifestA | Return the ZAP1 capability manifest: what this MCP covers, what it deliberately excludes, and how agents should compose it with wallet-layer tools. |
| zcash_receipt_templateB | Return a customer-ready ZAP1 receipt workflow for agent actions, payment receipts, operator lifecycle events, or policy attestations. |
| zcash_conformance_checkB | Validate a ZAP1 receipt packet against the frozen v1 receipt contract. Returns malformed, pending, or anchored. |
| zap1_wallet_receipt_requestB | Build a ZAP1 receipt request from a wallet-layer action result. The wallet keeps custody, signing, scanning, and broadcast; ZAP1 receives only bounded hashes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Frontier-Compute/zcash-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server