SwiftNodes RPC

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

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

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

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

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

Security scan

Recent checks