SwiftNodes MCP

Blockchain RPC for AI agents across 125+ chains: endpoint URLs, method support, endpoint probing, and RPC calls with your API key.

Hosted MCP Server

npx add-mcp 'https://rpc.swiftnodes.io/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

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.

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:

ToolWhat it does
rpc_callMake a JSON-RPC call on any SwiftNodes chain with your key (counts against your plan like any request).
get_accountYour 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

ToolWhat it does
list_chainsEvery chain SwiftNodes serves — name, slug, chain ID, category, docs page. Filterable.
get_chainFull detail for one chain: IDs, block time, native currency, HTTP/WebSocket/archive endpoint templates, docs links.
get_pricingLive flat-rate plans from the public API — rate limits, included features, no compute units.
get_method_supportWhich JSON-RPC methods work on which chain — auto-probed weekly through the same path customer requests take. Overview or per-method detail.
probe_endpointDiagnose 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 stdio

Via 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.