SwiftNodes RPC — Claude Code MCP server: chain data, endpoints, probes
Gives your agent a map of 128 blockchains: chain slugs, JSON-RPC method support, current pricing, and on-demand endpoint checks.
claude mcp add --transport http swiftnodes https://rpc.swiftnodes.io/mcpWhat SwiftNodes RPC does
The server answers chain questions from a bundled snapshot built off the SwiftNodes source of truth. get_chain returns block time, native currency and endpoint templates, while list_chains can be filtered down. Method support is re-probed weekly along the same route customer traffic takes, failover included. Pricing comes from the public plans API, with a bundled fallback when that call fails.
Four tools need no key at all: the chain lookups, pricing, the method matrix, and probe_endpoint. That last one inspects any EVM JSON-RPC URL and reports chain identity, block height, archive capability and latency. Supply a key and two more appear: rpc_call executes a method through SwiftNodes, and get_account returns your plan, rate limits, usage this month, plus any IP or origin limits. Key values themselves are never echoed back.
The hosted deployment saves you a setup step: point the client at https://rpc.swiftnodes.io/mcp over Streamable HTTP. Running it locally means stdio and Node 18 or newer, with no third-party packages. Since probe_endpoint will hit whatever http(s) address you hand it, send one quick pass rather than a load test.
What it helps with
- look up a chain slug and chain ID by name
- check whether trace_filter runs on BSC
- read the latest block on opBNB from chat
- compare plan rate limits before paying
- audit a third-party EVM endpoint for archive support
Example prompts for the agent
- List the SwiftNodes chains and show me Base with its chain ID
- Does opBNB support trace_filter?
- Run rpc_call on eth and give me the latest block number
How to install SwiftNodes RPC
1Platform CLI: remote server
claude mcp add --transport http swiftnodes https://rpc.swiftnodes.io/mcp2Platform CLI
claude mcp add swiftnodes-rpc -- npx -y swiftnodes-mcp1Platform CLI: remote server
codex mcp add swiftnodes-rpc --url https://rpc.swiftnodes.io/mcp2Platform CLI
codex mcp add swiftnodes-rpc -- npx -y swiftnodes-mcpConfig file
{
"mcpServers": {
"swiftnodes-rpc": {
"url": "https://rpc.swiftnodes.io/mcp"
}
}
}{
"mcpServers": {
"swiftnodes-rpc": {
"command": "npx",
"args": [
"-y",
"swiftnodes-mcp"
]
}
}
}Config file
{
"servers": {
"swiftnodes-rpc": {
"type": "http",
"url": "https://rpc.swiftnodes.io/mcp"
}
}
}{
"servers": {
"swiftnodes-rpc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"swiftnodes-mcp"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http swiftnodes-rpc https://rpc.swiftnodes.io/mcp2Platform CLI
gemini mcp add swiftnodes-rpc npx -y swiftnodes-mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about SwiftNodes RPC
How do I install SwiftNodes RPC in Claude Code?
Add the hosted endpoint with claude mcp add --transport http swiftnodes https://rpc.swiftnodes.io/mcp. To use the two key-only tools, pass your API key as an Authorization header in the config.
What does SwiftNodes RPC do?
It exposes chain details, live pricing and a JSON-RPC method matrix to the agent, and can call endpoints on request. An API key unlocks rpc_call and get_account.
What is required to run it locally?
Node 18 or newer, then npx -y swiftnodes-mcp or node swiftnodes-mcp/bin/server.js after cloning the repo. It has no external dependencies.
