Skip to content
SwiftNodes logo

SwiftNodes MCP server

Which servers in the official MCP registry are SwiftNodes's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to SwiftNodes

Whose server it is
  • Registry nameio.swiftnodes/swiftnodesverified in the MCP registry

The registry name sits under swiftnodes.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools7
  • Server calls itselfswiftnodes
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 469 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • For "route AI agent calls to chains via an MCP server", the likely first call is list_chains.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-20
  • INITE MCP score86 of 100answers 100 · definitions 98 · context 100 · use 30
  • Use32 npm downloads a week
  • Answered100% of days7 of 7 daily checks
  • Median first answer493 ms
  • Space in an agent's context≈ 661 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 98 of 100
  • Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 7

What an agent can do with it

  • not sure · send blockchain reads and writes through one API key
  • not sure · subscribe to live blockchain events over websocket
  • can do · route AI agent calls to chains via an MCP server

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-20
  • 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.

  • get_chain

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

  • get_pricing

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

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

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

  • 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…

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http swiftnodes https://rpc.swiftnodes.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://rpc.swiftnodes.io/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.