Swiftnodes MCP

What swiftnodes/swiftnodes-mcp MCP server does

The swiftnodes/swiftnodes-mcp MCP server exposes SwiftNodes data and RPC operations to MCP-compatible AI clients. It covers all 128 chains served by SwiftNodes, including Ethereum, BNB Smart Chain, opBNB, Base, Arbitrum, Polygon, Solana, and Bitcoin. Chain slugs are used in tool arguments and endpoint URLs.

The server is listed in the official MCP Registry as io.swiftnodes/swiftnodes. It fits the Developer Tools category for agents that need factual blockchain infrastructure information or direct endpoint diagnostics rather than application-specific wallet or contract abstractions.

How it works

The hosted deployment is available at https://rpc.swiftnodes.io/mcp over Streamable HTTP. Clients send an authorization header when using an API key. Without a key, the public discovery and diagnostic tools remain available. Supplying a key enables rpc_call and get_account; RPC requests count against the associated plan, while account results omit the key value itself.

Chain metadata comes from a bundled snapshot generated from SwiftNodes source data. Pricing is fetched from the public plans API, with bundled data available as a fallback. JSON-RPC method support comes from a live method matrix that is re-probed weekly through the customer request path, including failover behavior.

Setup and configuration

The hosted option requires no local installation. Configure an MCP client with the hosted URL and, when needed, an Authorization: Bearer header containing the SwiftNodes API key. Claude can be configured with its MCP command-line setup, while Cursor uses an MCP JSON configuration with the server URL and headers.

For local use, swiftnodes/swiftnodes-mcp runs with Node.js 18 or newer and has no dependencies. Clone the repository and start bin/server.js with Node; it communicates over stdio. The README also documents an npx command for the package once published. Claude Desktop and other MCP clients can launch the local server with node and the script path as arguments.

Tools and capabilities

• list_chains returns chain names, slugs, IDs, categories, and documentation links, with filtering support.
• get_chain provides chain identifiers, block time, native currency, HTTP, WebSocket, and archive endpoint templates, plus documentation links.
• get_pricing retrieves current flat-rate plans, rate limits, included features, and the absence of compute-unit pricing.
• get_method_support shows JSON-RPC support by chain, either as an overview or by method.
• probe_endpoint checks an EVM HTTP endpoint for chain identity, block height, archive capability, and latency, or executes a specified method call.
• rpc_call sends a JSON-RPC request to a SwiftNodes chain when an API key is supplied.
• get_account reports the key's plan, limits, monthly usage, and IP or origin restrictions without exposing the key.

Limitations and notes

probe_endpoint accepts any HTTP or HTTPS URL and is intended for a quick diagnostic pass, not load testing. The method-support results are based on periodic probes and may reflect the customer path and failover configuration. The local chain data is a generated snapshot and should be regenerated after chain changes. API-key-backed operations depend on the applicable SwiftNodes plan and limits.