zenith
Related Servers
Alternatives to zenith
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to simulate EVM bytecode and probe capabilities, serving as a gateway to an Ethereum execution engine.MIT

Pharos MCP Serverofficial
AlicenseAqualityDmaintenanceEnables querying Pharos blockchain data (EVM-compatible) through MCP, with read-only tools for blocks, transactions, balances, and contract calls, plus optional transaction broadcasting when self-hosted.14MIT- AlicenseAqualityDmaintenanceA read-only MCP server that queries multichain EVM on-chain data through Blockscout REST API, providing tools for address info, transactions, logs, and more.1620 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables proof-carrying project execution through a read-only remote MCP endpoint and WebMCP tools for managing Project Passports, task graphs, evidence-backed provider comparisons, route approvals, artifacts, verification records, and checkpoints without executing external providers.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local MCP clients to expose and execute typed tools through a bounded native runtime with Ed25519 admission, per-session budgets, rate limits, schemas, and cached outputs.AGPL 3.0

Tarmac MCPofficial
AlicenseAqualityBmaintenanceEnables MCP agents such as Claude and Cursor to start runs on a live Robinhood Chain fork, read balances and quotes, request swaps under policy checks, and review verdicts and traces without holding a key.8MIT
TDQS
Scored across 20 tools
Most tools have clear distinct roles, especially the gateway_* transfer/status tools versus the zenith_* chain utilities. A few pairs overlap conceptually, such as gateway_deposit_status vs zenith_get_transaction and gateway_activity vs zenith_get_logs, but the descriptions clarify when each should be used.
Names are consistently snake_case and grouped by gateway_ and zenith_ prefixes. The pattern mixes noun phrases like gateway_tokens and zenith_network_info with verb phrases like zenith_get_logs and gateway_convert, but it remains predictable and readable.
20 tools is above the typical 3-15 range but reflects a broad EVM plus Canton Gateway domain. Each tool appears to serve a specific workflow such as preflight, deploy, verify, logs, config, or sending, so the count is justified rather than padded.
Coverage is broad: network info, account/contract reads, logs, decoded transactions, gateway transfer preflight and status, deployment, verification, project config, compatibility checks, and sending. Minor gaps exist, such as no faucet request tool or explicit transaction replacement/cancel, but core lifecycle workflows are covered.