SwiftNodes MCP

An official MCP server provided by SwiftNodes that allows AI agents to interact with blockchain RPC endpoints across 128+ chains. It enables listing supported chains, checking method support, probing endpoints, and executing read-only JSON-RPC calls using the user's API key, while enforcing safety limits to prevent transaction signing or broadcasting.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by SwiftNodes

MCP endpoint (Streamable HTTP)

https://rpc.swiftnodes.io/mcp

Vendor documentation

What you can do with it

List all supported blockchain chains and their status
Check which JSON-RPC methods are supported on a specific chain
Probe public endpoints for latency and archive capability
Execute read-only JSON-RPC calls on any supported chain

Tools advertised by the last live check:

list_chains
get_chain
get_pricing
get_method_support
probe_endpoint
rpc_call
get_account

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add swiftnodes-mcp --url https://rpc.swiftnodes.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable swiftnodes-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start swiftnodes-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "swiftnodes-mcp": {
      "serverUrl": "https://rpc.swiftnodes.io/mcp"
    }
  }
}

See all 1,218

Do you run SwiftNodes MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing