shardeum_getNodeListLABSCO SUMMARY
Chain inspection stops being a folder of one-off scripts.
The node, cycle and account views sit next to the standard Ethereum calls behind one validated interface, so a debugging question can move from network state down to a single transaction receipt without switching tools.
What it is
Shardeum's network and RPC operations exposed as thirteen tools: three that are Shardeum-specific and ten standard Ethereum JSON-RPC methods. Requests are schema-validated before they go out, and network and RPC failures are handled rather than passed through raw.
What you get
- Shardeum-specific state: the node list, the network account, and cycle information
- Blocks by number or by hash, plus the receipts for a whole block in one call
- Transactions by hash and their receipts, and the transaction count for an account
- Account balance, chain id, and gas estimation for a call you have not sent yet
- Structured responses back to the agent rather than raw RPC envelopes
Requirements
Node, with the repository's dependencies installed, and a Shardeum RPC endpoint to point at. Every tool here reads — nothing signs or sends a transaction.
Setup effort
Build from source — get the source, then follow the project's own run instructions
USE CASES
01
Finding out why a transaction did not do what you expected
Fetch the transaction by hash and then its receipt, so the status, the gas actually used and the logs emitted are read together.
02
Checking the health of the network
Read the node list and the current cycle information alongside the network account, which is the Shardeum-specific view a generic Ethereum tool cannot give you.
03
Investigating an account
Read its balance and its transaction count together — the nonce is what tells you whether a stuck transaction is actually stuck.
04
Looking at what happened in a block
Pull the block by number or hash, then take all its receipts in one call rather than fetching them transaction by transaction.
05
Costing a call before you send it
Estimate the gas for the transaction you are planning, against the right chain id, so a fee surprise happens in the estimate rather than on chain.
13 tools
Listed in project docs. Your client may show a different list.
shardeum_getNetworkAccountshardeum_getCycleInfoeth_blockNumbereth_getBlockByHasheth_getBlockByNumbereth_getBlockReceiptseth_getTransactionByHasheth_getTransactionReceipteth_getTransactionCounteth_getBalanceeth_estimateGaseth_chainIdBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation.
Requires
node on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
node <YOUR_PATH_TO_SHARDEUM_MCP_SERVER>/index.jsMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"shardeum-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SHARDEUM_MCP_SERVER>/index.js"
]
}
}
}
