Zero Network MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zero_overviewA | Get a comprehensive overview of the Zero Network — what it is, how it works, key facts, and links. |
| zero_transaction_formatB | Get the Zero transaction wire format (136 bytes), account state format (48 bytes), and cryptographic primitives. |
| zero_python_sdkB | Get Python SDK documentation — installation, wallet creation, sending Z, bridge operations, environment variables. |
| zero_javascript_sdkB | Get JavaScript SDK documentation — installation, wallet creation, sending Z, environment variables. |
| zero_x402_integrationB | Get x402 HTTP payment protocol integration guide — server middleware (Python/JS), client auto-pay, 402 response format. |
| zero_mcp_paymentsA | Get MCP server payment integration guide — how to charge AI agents per tool call, payment flow, spending limits. |
| zero_api_referenceA | Get the Zero Network API reference — all 8 gRPC endpoints: Send, GetTransfer, GetHistory, GetBalance, GetAccount, BridgeIn, BridgeOut, GetBridgeStatus. |
| zero_network_parametersA | Get all Zero Network parameters — fees, limits, staking, slashing, circuit breaker thresholds, pruning rules. |
| zero_validator_infoB | Get validator documentation — hardware requirements, staking, trust scoring, slashing rules, economics. |
| zero_security_modelB | Get the Zero security model — attack mitigations, Trinity Validators, vault contract security, bridge protections. |
| zero_implementation_guideA | Get step-by-step implementation guide for accepting Zero payments — API providers (x402), MCP servers, website paywalls, pricing guidelines. |
| zero_convertC | Convert between USD, Z tokens, and units. Args: amount: The amount to convert direction: One of "usd_to_z", "z_to_usd", "z_to_units", "units_to_z" |
| zero_estimate_costC | Estimate the cost of operating on Zero Network. Args: num_transactions: Number of transactions to estimate for avg_amount_z: Average transaction amount in Z (default 0.10 Z) |
| zero_pricing_calculatorC | Calculate expected revenue for a Zero-gated service. Args: price_per_call_z: Price per API/tool call in Z daily_calls: Expected number of calls per day |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes, such as API reference, conversion, cost estimation, and SDK documentation, but there is some overlap between 'zero_implementation_guide', 'zero_mcp_payments', and 'zero_x402_integration', which all cover payment integration aspects and could cause mild confusion. The descriptions help differentiate them, but boundaries are not perfectly clear.
All tool names follow a consistent 'zero_' prefix with descriptive snake_case suffixes, such as 'zero_api_reference', 'zero_convert', and 'zero_estimate_cost'. This pattern is maintained throughout all 14 tools, making them predictable and easy to identify.
With 14 tools, the count is reasonable for a server focused on Zero Network documentation, integration, and utilities. It's slightly on the higher side but well-scoped for the domain, covering various aspects like APIs, SDKs, security, and pricing without feeling overly bloated.
The tool set provides comprehensive coverage for the Zero Network domain, including API references, SDK documentation (JavaScript and Python), implementation guides, security models, transaction details, and utility tools like conversion and cost estimation. There are no obvious gaps, and it supports a full lifecycle from learning to integration and operation.