Skip to main content
Glama
swiftnodes-mcp

swiftnodes-mcp

Official

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)

bsc

https://rpc.swiftnodes.io/rpc/bsc?key=YOUR_API_KEY

opBNB

opbnb

https://rpc.swiftnodes.io/rpc/opbnb?key=YOUR_API_KEY

Ethereum

eth

https://rpc.swiftnodes.io/rpc/eth?key=YOUR_API_KEY

Base

base

https://rpc.swiftnodes.io/rpc/base?key=YOUR_API_KEY

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

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

rpc_call

Make a JSON-RPC call on any SwiftNodes chain with your key (counts against your plan like any request).

get_account

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

list_chains

Every chain SwiftNodes serves — name, slug, chain ID, category, docs page. Filterable.

get_chain

Full detail for one chain: IDs, block time, native currency, HTTP/WebSocket/archive endpoint templates, docs links.

get_pricing

Live flat-rate plans from the public API — rate limits, included features, no compute units.

get_method_support

Which JSON-RPC methods work on which chain — auto-probed weekly through the same path customer requests take. Overview or per-method detail.

probe_endpoint

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

Available Tools

5 tools
get_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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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 npm
      MIT