SwiftNodes RPC

io.swiftnodesPublished by swiftnodes.ioOfficial publisherv1.0.1Updated Oct 30, 2026

Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.

VerifiedStreamable HTTPWeb executableCloud & Infrastructure Finance Developer Tools

Server details

Identifier: io.swiftnodes/swiftnodes
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 15, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to swiftnodes.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.swiftnodes%2Fswiftnodes.svg)](https://sourceweft.com/mcp/io.swiftnodes%2Fswiftnodes?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

SwiftNodes RPC gives an assistant live data on 125+ blockchain RPC chains, JSON-RPC method support and pricing, plus keyed RPC calls and endpoint probing.

What you can do: List and inspect chains: names, slugs, chain IDs, live status, block height and HTTP/WebSocket/archive endpoint templates
Check JSON-RPC method support per chain and read current flat-rate plans and rate limits
Probe any public EVM JSON-RPC endpoint for chain ID, block height, archive capability and latency, or run a specific method call against it
Make read-only JSON-RPC calls on SwiftNodes chains with your own API key
Show your account plan, rate limits, monthly usage and key IP/origin restrictions
When to use it: Useful when an assistant needs factual, current answers about blockchain networks, which JSON-RPC methods a chain supports, or SwiftNodes pricing, and when you want it to run read-only RPC queries or diagnose an EVM endpoint without leaving the chat.
Requirements: Either the hosted Streamable HTTP endpoint or a local stdio process (Node.js 18 or newer, no dependencies; also available as an npm package). An optional SwiftNodes API key is passed as an Authorization bearer header; without it only the public lookup tools work.

Before you install

The API key is sent as an Authorization bearer header to the server; keep it out of shared configs. Keyed rpc_call requests count against your plan's quota. probe_endpoint will call any http(s) URL supplied to it, so point it only at endpoints you are allowed to query and avoid load testing. Transaction-sending and signing methods are refused.

Installation

In SourceWeft

Open SwiftNodes RPC in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.swiftnodes%2Fswiftnodes/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "swiftnodes-rpc": {
      "type": "http",
      "url": "https://rpc.swiftnodes.io/mcp"
    }
  }
}

README

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.

Hosted server (recommended)

SwiftNodes runs this server for you at https://rpc.swiftnodes.io/mcp (Streamable HTTP). Nothing to install.

bash

claude mcp add --transport http --scope user swiftnodes https://rpc.swiftnodes.io/mcp --header "Authorization: Bearer $SWIFTNODES_API_KEY"

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):

json

{ "mcpServers": { "swiftnodes": { "url": "https://rpc.swiftnodes.io/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

{ "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:

bash

git clone https://github.com/swiftnodes/swiftnodes-mcpnode swiftnodes-mcp/bin/server.js   # speaks MCP over stdio

git clone https://github.com/swiftnodes/swiftnodes-mcpnode swiftnodes-mcp/bin/server.js   # speaks MCP over stdio

Via npm (once published): npx -y swiftnodes-mcp

Claude Desktop

json

{  "mcpServers": {    "swiftnodes": {      "command": "node",      "args": ["/path/to/swiftnodes-mcp/bin/server.js"]    }  }}

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

Source: README.md at commit c47ed23

Tools

list_chains

List every blockchain SwiftNodes serves (one API key for all): name, slug, chain ID, live status, and whether WebSocket and archive (?archive=1) are available.

Parametersqueryevm_only

get_chain

One chain in detail: chain ID, live status and block height, and the HTTP, WebSocket and archive endpoint URL templates.

Parameterschainrequired

get_pricing

SwiftNodes plans: flat monthly price, HTTP and WebSocket rate limits. No compute units, no per-request billing.

Takes no parameters.

get_method_support

Which JSON-RPC methods work on which chain, probed weekly through the customer request path. No args for the overview, or {method} for per-chain detail.

Parametersmethod

probe_endpoint

Diagnose any public EVM JSON-RPC endpoint. With {url}: chain ID, block height, archive capability and latency. With {url, method, params}: makes that call and returns the result.

Parametersurlrequiredmethodparams

rpc_call

Make a JSON-RPC call on any SwiftNodes chain with the caller's API key (sent to this MCP server as 'Authorization: Bearer <key>'). Counts against that key's plan like any other request. Read-only: methods that send or sign transactions are refused.

Parameterschainrequiredmethodrequiredparamsarchive

get_account

The caller's SwiftNodes plan, rate limits, requests used this month, and the IP/origin restrictions on the key in use. Needs 'Authorization: Bearer <key>'. Never returns key values.

Takes no parameters.

Version history

v1.0.1LatestOct 15, 2026

Score

100% 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 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts