SwiftNodes RPC

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.swiftnodes/swiftnodes and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 15 Oct 2026. Not supplied by the maker.

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

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

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.