swiftnodes-mcp
OfficialSummary: swiftnodes-mcp is an MCP server that gives AI agents live access to SwiftNodes' multi-chain blockchain RPC data — chains, pricing, JSON-RPC method support — plus a generic EVM endpoint prober.
list_chains— Browse every chain SwiftNodes serves (README says 128; the tool description says 75+ — an inconsistency worth flagging), with name, slug, chain ID, category and docs page. Filter by name/slug substring orevm_only.get_chain— Full detail for one chain: chain ID, category, block time, native currency, HTTP/WebSocket/archive endpoint URL templates, docs links. Requireschain(name or slug).get_pricing— Live flat-rate monthly plans, HTTP/WS rate limits and included features; no compute units. Takes no arguments.get_method_support— Shows which JSON-RPC methods (e.g.trace_filter,eth_getProof, batching, archive) work on which chain, auto-probed weekly via the real customer path. No args = overview,{method}= per-chain detail.probe_endpoint— Diagnose any EVM JSON-RPC endpoint (SwiftNodes' or anyone's): chain identity, block height, archive capability and latency with just{url}, or run a specific method call with{url, method, params}.With an API key (hosted server only):
rpc_callto make real JSON-RPC calls on any SwiftNodes chain (counts against your plan), andget_accountto view your plan, rate limits, monthly usage and IP/origin restrictions (never key values).Access: hosted at
https://rpc.swiftnodes.io/mcp(Streamable HTTP, key optional) or run locally over stdio with Node ≥ 18; registered asio.swiftnodes/swiftnodes.
Provides access to Bitcoin through SwiftNodes multi-chain RPC, enabling chain details, method support lookup, and JSON-RPC operations.
Provides access to Ethereum through SwiftNodes multi-chain RPC, enabling chain details, JSON-RPC method support checks, endpoint probing, and direct RPC calls.
Provides access to Polygon through SwiftNodes multi-chain RPC, enabling chain details, JSON-RPC method support lookup, endpoint probing, and direct RPC calls.
Provides access to Solana through SwiftNodes multi-chain RPC, enabling chain details, method support lookup, and JSON-RPC operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@swiftnodes-mcp What JSON-RPC methods are supported on Base?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
swiftnodes-mcp
An MCP (Model Context Protocol) server for SwiftNodes — multi-chain blockchain RPC, exposed to AI agents.
One API key, 125+ chains, flat-rate pricing. This server gives Claude, ChatGPT, Cursor, and any MCP client live, factual answers about chains, pricing, and JSON-RPC method support — plus the ability to probe any EVM endpoint directly.
Chains
Works across all 128 SwiftNodes chains, including Ethereum, BNB Smart Chain (BSC), opBNB, Base, Arbitrum, Polygon, Solana and Bitcoin. Each chain has a slug used in tool arguments and endpoint URLs, for example:
Chain | Slug | Endpoint |
BNB Smart Chain (BSC) |
|
|
opBNB |
|
|
Ethereum |
|
|
Base |
|
|
Example prompts: "Which JSON-RPC methods does BNB Smart Chain support?", "What is the latest block on opBNB?", "Is trace_filter available on BSC?". list_chains returns the full list.
Related MCP server: chain-data
Hosted server (recommended)
SwiftNodes runs this server for you at https://rpc.swiftnodes.io/mcp (Streamable HTTP). Nothing to install.
claude mcp add --transport http --scope user swiftnodes https://rpc.swiftnodes.io/mcp --header "Authorization: Bearer $SWIFTNODES_API_KEY"Cursor and other clients (~/.cursor/mcp.json):
{ "mcpServers": { "swiftnodes": { "url": "https://rpc.swiftnodes.io/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }The key is optional: without it the public tools below work. With it, two more tools are available:
Tool | What it does |
| Make a JSON-RPC call on any SwiftNodes chain with your key (counts against your plan like any request). |
| Your plan, rate limits, requests used this month, and the IP/origin restrictions on the key. Never returns key values. |
Listed in the official MCP Registry as io.swiftnodes/swiftnodes. Docs: https://swiftnodes.io/docs/mcp
Tools
Tool | What it does |
| Every chain SwiftNodes serves — name, slug, chain ID, category, docs page. Filterable. |
| Full detail for one chain: IDs, block time, native currency, HTTP/WebSocket/archive endpoint templates, docs links. |
| Live flat-rate plans from the public API — rate limits, included features, no compute units. |
| Which JSON-RPC methods work on which chain — auto-probed weekly through the same path customer requests take. Overview or per-method detail. |
| Diagnose any EVM JSON-RPC endpoint (ours or anyone's): chain identity, block height, archive capability, latency — or run a specific method call. |
Run it locally (stdio)
Zero dependencies, Node >= 18.
From this repo:
git clone https://github.com/swiftnodes/swiftnodes-mcp
node swiftnodes-mcp/bin/server.js # speaks MCP over stdioVia npm (once published): npx -y swiftnodes-mcp
Claude Desktop
{
"mcpServers": {
"swiftnodes": {
"command": "node",
"args": ["/path/to/swiftnodes-mcp/bin/server.js"]
}
}
}Cursor / any MCP client
Add a stdio server with command node and args ["/path/to/swiftnodes-mcp/bin/server.js"].
Data sources
Chains — bundled snapshot generated from the SwiftNodes site source of truth (
scripts/generate-chains-data.mjs; regenerate after chain changes).Pricing — fetched live from
https://rpc.swiftnodes.io/api/plans(bundled fallback if unreachable).Method support — fetched live from
https://swiftnodes.io/method-matrix.json, re-probed weekly. Support values reflect the real customer path, including failover.
Notes
probe_endpoint will call any http(s) URL you give it — the same ground our CLI diagnostic rpc-doctor covers. Probe responsibly: one quick pass per endpoint, not a load test.
Questions: swiftnodes.io — free tier, no KYC.
License
MIT — see LICENSE.
Available Tools
5 toolsget_chainAInspect
Full details for one chain SwiftNodes serves: chain ID, category, block time, native currency, HTTP/WebSocket/archive endpoint URL templates, and docs links.
Inputs: chain (required).
get_method_supportAInspect
Which JSON-RPC methods work on which chain, auto-probed weekly through the real customer path (eth_getProof, trace_block, trace_filter, batching, archive, and more). Call with no args for the overview, or {method} for per-chain support.
Inputs: method.
get_pricingAInspect
Live flat-rate pricing for SwiftNodes RPC: monthly plans, HTTP/WS rate limits, included features. No per-request fees or compute units.
Inputs: no named parameters.
list_chainsAInspect
List every blockchain SwiftNodes serves (75+ chains, one API key for all). Returns name, slug, chain ID, category, and docs page per chain. Use before get_chain if unsure of the exact chain name.
Inputs: query, evm_only.
probe_endpointAInspect
Diagnose ANY EVM JSON-RPC endpoint (ours or anyone's). With {url} only: checks chain identity, block height, and archive capability with latency. With {url, method, params}: performs that exact JSON-RPC call and returns the result or error.
Inputs: url (required), method, params.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing chains, fetching one chain's details, getting pricing, checking method support, and probing arbitrary endpoints. No two tools overlap in a way that would cause an agent to select the wrong one.
All tool names follow a consistent snake_case verb_noun pattern: list_chains, get_pricing, get_chain, get_method_support, probe_endpoint. The verbs and nouns are predictable and match the action each tool performs.
Five tools is well-scoped for this server's purpose: catalog discovery, detail lookup, pricing, capability checking, and endpoint diagnostic. Each tool earns its place and there is no bloat.
The domain is SwiftNodes' chain and RPC support surface, and the tools cover discovery, detail, pricing, method compatibility, and live diagnosis. There are no obvious dead ends or critical missing operations for the stated purpose.
Maintenance
Related MCP Connectors
RPC gateway for agents: six mainnets, measured failover, a key without signup, pay per call in USDC.
ChainRay provides multi-chain blockchain data and intelligence for AI agents through 79 MCP tools across 57 supported networks, covering gas, chain data, wallets, DeFi, market, security, monitoring, and verifiable proofs. MCP access is available at https://mcp.chainray.online/mcp; paid HTTP capabilities settle via x402 on Base.
EVM chain reads for agents: balances, gas, fees, blocks, txs, logs, ENS. 15 tools, x402 per call.
Verified EVM, Aptos and finance tools for AI agents; gas for 14 chains. Pay per call (x402).
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query blockchain chain data, including chain details, RPC endpoints, and chain relationships, through a Model Context Protocol server.6PolyForm Noncommercial 1.0.0
- AlicenseAqualityCmaintenanceEnables AI agents to fetch live multi-chain portfolio, token info, gas prices, and token prices across Ethereum, Base, Polygon, Arbitrum, and Optimism with a single call. No API key required.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query on-chain data across EVM chains like Base, Optimism, Avalanche, Celo, and Arbitrum, including balances, transactions, gas, and smart contract interactions.53 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to use keyless multi-chain EVM JSON-RPC, an indexed Data API, documentation, pricing, and status tools, with optional API-key access for account and deposit operations.1516 npm3MIT