
Nodeflare Mcp
io.github.Nodeflare-appPublished by GitHub account Nodeflare-appv0.8.0Updated Oct 24, 2026
Blockchain JSON-RPC on 23 EVM chains for AI agents - free tier, API key, or x402 pay-per-call.
Overview
Read-only blockchain JSON-RPC access across 23 EVM chains, letting an assistant query balances, transactions, logs, gas and token data.
- What you can do
- Exposes JSON-RPC tools for 23 EVM chains: list_chains, get_block_number, get_balance, get_transaction, get_transaction_receipt, get_block, eth_call, rpc_call, get_gas_price, compare_gas, get_token_balance, get_token_metadata, get_token_price, resolve_ens and get_multichain_balances. Heavier tools include get_logs, get_token_allowances, get_wallet_report, check_token_safety, simulate_transaction and onchain_answer. It also ships MCP prompts and Claude Code slash-command recipes for common queries.
- When to use it
- Useful when an assistant needs on-chain data without running its own node: checking balances or token holdings, inspecting a transaction or contract logs, comparing gas across chains, or pre-flight checking a token or transaction.
- Requirements
- Runs locally via npx (Node.js). Standard reads need no key. Heavy methods need either NODEFLARE_API_KEY or X402_PRIVATE_KEY; the latter is an EVM wallet private key holding USDC on Base, Polygon or Arbitrum. Network access to NodeFlare endpoints and DefiLlama is required.
Installation
In SourceWeft
- Open Nodeflare Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
NodeFlare MCP Server
Blockchain JSON-RPC for AI agents on 23 EVM chains — Ethereum, Base, BNB Chain, Arbitrum, Optimism, Avalanche, HyperEVM, Polygon, and young chains like Robinhood Chain, Plasma, Ink, Zircuit, BOB and Soneium. Served from NodeFlare's own bare-metal nodes across 5 regions.
Quick start
That's it — no API key required for standard reads (block numbers, balances, transactions, eth_call).
Every tool's chain argument accepts a slug (eth, base, arb), a name (ethereum, arbitrum, bsc), or a numeric chain ID (1, 8453) — so agents don't have to know NodeFlare's internal slugs.
Install as a Claude Code plugin
This repo doubles as a Claude Code plugin marketplace. Installing the plugin wires up the MCP server and a set of slash-command recipes in one step:
Then use the recipes below (/nodeflare:balance, /nodeflare:token, …). To unlock heavy methods, export NODEFLARE_API_KEY in your shell before starting Claude Code (free key, 2M CU/month).
Recipes
Ready-made slash commands bundled with the plugin:
Access tiers
The server picks its access tier from the environment:
With an x402 wallet, a blocked heavy method is retried automatically as a paid call — the tool result includes "_x402": "settled via x402" when a payment settled on-chain.
Use a dedicated agent wallet holding a small USDC balance — never your main wallet.
Tools
Address arguments (get_balance, get_token_balance, eth_call) also accept ENS names — pass vitalik.eth and it's resolved to an address automatically.
get_multichain_balances can also auto-discover the tokens an address holds (discover: true, x402 wallet required). Discovered tokens are USD-priced via DefiLlama and, on price-covered chains, filtered by value: pass minUsd (default 0.01) to set the worthless-token cutoff, includeSpam: true to keep unpriced tokens, or includeDust: true to keep sub-1e-9 balances.
Prompts (any MCP client)
The server also exposes the recipes as MCP prompts, so guided workflows show up in any MCP client (Cursor, Windsurf, …), not just the Claude Code plugin: chains, balance, token, tx, logs, gas.
Links
- NodeFlare — free API key, 2M CU/month
- x402 pay-per-request — pricing and how it works
- Docs · Status · Discord
MIT
Source: README.md at commit 82999f5
Tools
0Version history
1- v0.8.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts