RouteMesh MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROUTEMESH_API_KEY | Yes | Your RouteMesh API key. Required to authenticate and route RPC requests. | |
| ROUTEMESH_BASE_URL | No | Primary RouteMesh API base URL. Defaults to the public RouteMesh API. | |
| ROUTEMESH_MGMT_TOKEN | No | Optional customer management token. When set, the server exposes customer-scoped tools (and provider-scoped tools if the token's customer is linked to a provider). | |
| ROUTEMESH_API_SERVER_URL | No | Base URL for the RouteMesh API server used by rpc_list_chains (GET /chains). | |
| ROUTEMESH_BACKUP_BASE_URL | No | Backup RouteMesh API base URL used on retryable failures after ROUTEMESH_BASE_URL. |
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 |
|---|---|
| rpc_list_chainsA | Discover supported chains from RouteMesh API server (GET /chains) and filter by chain ID or name query. |
| rpc_callB | Call any JSON-RPC method on a RouteMesh-supported chain. Useful as an escape hatch. |
| rpc_get_blockC | Fetch block data by block number/tag or by block hash on a given chain. |
| rpc_get_transactionC | Fetch a transaction by hash. |
| rpc_get_transaction_receiptC | Fetch a transaction receipt by hash. |
| rpc_get_logsB | Query indexed logs/events with block range and topic filters. |
| rpc_get_balanceC | Fetch the native token balance for an address. |
| rpc_call_contractA | Execute a read-only contract call via eth_call using pre-encoded calldata. |
| rpc_estimate_gasB | Estimate gas for a transaction request. |
| rpc_get_fee_dataA | Fetch current gas price, max priority fee and a one-block fee history sample. |
| rpc_trace_transactionC | Attempt transaction tracing using trace_transaction or debug_traceTransaction. |
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 11 tools
Each tool targets a specific RPC operation (block, transaction, receipt, logs, balance, contract, gas, fee, trace), making them clearly distinct. The only minor overlap is between rpc_call and rpc_call_contract, but their descriptions clarify that rpc_call is a generic escape hatch while rpc_call_contract is specifically for eth_call with pre-encoded calldata.
All tools follow a consistent rpc_<verb>_<noun> pattern with snake_case throughout, such as rpc_get_block, rpc_estimate_gas, and rpc_list_chains. The lone rpc_call is a deliberate generic exception but still fits the rpc_ prefix convention.
11 tools is a well-scoped size for an RPC-focused server, covering the most common blockchain read operations without unnecessary bloat. Each tool addresses a distinct need, and the count aligns with the server's apparent purpose as a multi-chain RPC gateway.
The set covers all essential RPC query operations: chain discovery, blocks, transactions, receipts, logs, balances, contract reads, gas estimation, fee data, and tracing. The inclusion of a generic rpc_call escape hatch ensures any missing method can still be invoked, so there are no significant coverage gaps.