moltnode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MOLTNODE_URL | No | Point at a self-hosted gateway. | https://moltnode.ag |
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 |
|---|---|
| list_chainsA | List every chain MoltNode can reach (slug, name, chainId, family, native currency). Use the |
| rpc_callA | Make any JSON-RPC 2.0 call against a chain through MoltNode. Works for EVM (eth_*), Solana (getSlot, getAccountInfo), and Sui. It is the general-purpose tool, so prefer it whenever no convenience tool fits. |
| get_block_numberA | Latest block height / slot for an EVM, Solana, or Sui chain. |
| get_balanceB | Native-token balance of an address on an EVM chain, returned in wei and as a decimal of the native currency. |
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 4 tools
Each tool has a clearly distinct purpose: listing chains, making arbitrary RPC calls, fetching block number, and getting balance. No overlap.
All tools use consistent snake_case verb_noun pattern: list_chains, rpc_call, get_block_number, get_balance.
4 tools is appropriate for a blockchain RPC proxy: a chain enumerator, a general-purpose RPC caller, and two convenience helpers for common queries.
The set covers core functionality (chain list, arbitrary RPC, block height, balance) but lacks convenience tools for other common operations like getting transactions or logs. However, rpc_call can fill those gaps.