Zcash MCP server

Connect your assistant

Add a remote MCP server in your assistant’s connector settings and use this URL for the selected network, mainnet:

https://api.zecblock.com/v1/mcp

Choose Streamable HTTP and no authentication for the public API. Protected previews require their own preview key. Your assistant must support remote MCP servers; availability depends on the client.

Claude Code:

claude mcp add --transport http zecblock https://api.zecblock.com/v1/mcp

Codex:

codex mcp add zecblock --url https://api.zecblock.com/v1/mcp

For a client with an MCP configuration file:

{
  "mcpServers": {
    "zecblock": {
      "url": "https://api.zecblock.com/v1/mcp"
    }
  }
}

Try asking “What is the latest indexed Zcash block?”, “Show the public pool balances” or “Look up this transaction” with its complete hash. Answers come from your chosen assistant; inspect the returned source URL and metadata.

20 public read tools

The connector uses the same validated responses as the REST API. Availability varies by network and source. Mainnet cross-chain tools distinguish indexed NEAR history from recent Maya and THORChain observations.

• chain_info — Current indexed chain height.
• blocks — Recent canonical blocks. Continue with meta.page cursors.
• block — One block by height or full hash, including canonical/orphan context.
• transactions — Recent public transaction records. Encrypted fields remain unavailable.
• transaction — One transaction by its complete hash. Public facts do not reveal encrypted recipients or amounts.
• mempool — Observed pending transactions. This is a transient node observation.
• address — Public activity of a transparent address. Does not accept private or viewing keys.
• network_supply — Supply accounting with the source response units and availability.
• network_accounting — Observed protocol fee, reserve and supply accounting. Unknown is not zero.
• network_fees — Observed network fees and their source-defined periods.
• network_halving — Network subsidy and halving schedule. Estimates are not confirmed activation times.
• pool_overview — Public aggregate shielded-pool balances, not individual shielded balances.
• pool_history — Historical aggregate pool balances with source coverage.
• pool_activity — Pool involvement counts and shares. A transaction may involve multiple pools.
• crosschain_analytics — Indexed NEAR 1Click analytics only; retain coverage and status exclusions.
• crosschain_swaps — Indexed NEAR 1Click swaps; provider-observed outcomes are not a census of all venues.
• crosschain_venues — Recent native-ZEC Maya or THORChain actions. A bounded provider feed, not complete indexed history or NEAR totals.
• crosschain_venue_analytics — Indexed Maya or THORChain history, flows, rankings and outcomes. Preserve traversal coverage and valuation basis.
• crosschain_venue_swaps — Indexed Maya or THORChain swap/refund actions with venue-bound pagination and exact full legs.
• reorg_summary — Locally observed reorg and orphan statistics; retain observer/coverage limits.

Custom SQL

Two more tools let your assistant write its own SQL over the same public datasets as Zift. Your assistant’s model writes the query; ZecBlock only validates and runs it.

• sql_catalogue — datasets, columns, units, query rules and worked examples. No key needed. Read it first.
• sql_query — runs one read-only SELECT (CTEs, joins and window functions allowed) and returns up to 200 rows with units, coverage and a result fingerprint. Rejected SQL returns the reason, so your assistant can fix it.

No key is needed: the setup commands above are enough. All MCP queries share a site-wide allowance per minute and per UTC day, so Zift stays available; nothing that identifies you or your IP address is stored. Queries are read-only and limited to 200 rows.

Need more? ZecBlock can issue an API key with higher limits. Send it as Authorization: Bearer <key>; in Claude Code add --header "Authorization: Bearer <key>" to the command above, and in Codex set bearer_token_env_var in ~/.codex/config.toml so the key stays in an environment variable.

Try asking “Using sql_query, how did the Orchard pool balance change over the last 30 days?” or “Which miners found the most blocks this week?”.

Data, privacy and limits

Zatoshi amounts remain exact decimal strings. Keep the response’s network, observation time, freshness, coverage and cursor metadata. Unknown is not zero; pool balances do not reveal individual shielded balances or transaction histories.

The connector accepts public read tools and read-only SQL over the public datasets. It does not accept viewing keys or private keys, and does not broadcast transactions or run paid AI requests. Tool queries are sent to ZecBlock; your assistant provider receives the conversation and results under its own terms. Read our privacy policy.

Each process permits 60 MCP requests per client IP per minute and 16 concurrent requests. Requests are limited to 16 KiB and 15 seconds (25 seconds while SQL tools are enabled); tool results are limited to 1 MiB. Paginated tools default to 10 items and allow at most 25. Existing upstream timeouts and host rate limits also apply. A result that exceeds the limit returns an error; use a smaller page or the REST API.

Streamable HTTP uses POST with JSON responses and no persistent sessions. There is no GET event stream. Browse the API reference and exact field conventions.