# SwiftNodes RPC (remote · rpc.swiftnodes.io)

Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `rpc.swiftnodes.io`: 72/100 (this document), [markdown](https://verifymcp.io/servers/io-swiftnodes-swiftnodes/rpc.md), [page](https://verifymcp.io/servers/io-swiftnodes-swiftnodes/rpc)
- npm · `swiftnodes-mcp`: 74/100, [markdown](https://verifymcp.io/servers/io-swiftnodes-swiftnodes/swiftnodes-mcp.md), [page](https://verifymcp.io/servers/io-swiftnodes-swiftnodes/swiftnodes-mcp)

## Channel facts

- Endpoint: `https://rpc.swiftnodes.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 570 tokens (~81/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SwiftNodes RPC MCP server?

SwiftNodes RPC is a hosted endpoint at https://rpc.swiftnodes.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.io-swiftnodes-swiftnodes]
url = "https://rpc.swiftnodes.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-swiftnodes-swiftnodes": {
      "type": "remote",
      "url": "https://rpc.swiftnodes.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-swiftnodes-swiftnodes --url 'https://rpc.swiftnodes.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-swiftnodes-swiftnodes:
    url: "https://rpc.swiftnodes.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-swiftnodes-swiftnodes": {
      "Transport": "http",
      "Url": "https://rpc.swiftnodes.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-swiftnodes-swiftnodes -t streamable-http -u 'https://rpc.swiftnodes.io/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 69)

First indexed and scored.

## MCP tools (7)

### `list_chains` (~83 tokens)

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.

Input parameters:

- `evm_only` (boolean): Only EVM chains.
- `query` (string): Optional name or slug filter, e.g. 'base' or 'zksync'.

### `get_chain` (~61 tokens)

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

Input parameters:

- `chain` (string, required): Chain slug, name or chain ID, e.g. "eth", "Base", "4663".

### `get_pricing` (~33 tokens)

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

### `get_method_support` (~62 tokens)

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.

Input parameters:

- `method` (string): e.g. 'trace_filter' or 'eth_getProof'.

### `probe_endpoint` (~76 tokens)

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.

Input parameters:

- `method` (string)
- `params` (array)
- `url` (string, required): Public http(s) RPC URL.

### `rpc_call` (~132 tokens)

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.

Input parameters:

- `archive` (boolean): Route to archive upstreams (paid plans).
- `chain` (string, required): Chain slug, e.g. "eth", "base", "robinhood". See list_chains.
- `method` (string, required): e.g. "eth_blockNumber".
- `params` (array): Method params, default [].

### `get_account` (~49 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/rpc#diagnostics

## Score history

- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 69
- 2026-10-15: 69

## Common questions

### What is the SwiftNodes RPC MCP server?

SwiftNodes RPC is an MCP server listed in the public MCP registry as io.swiftnodes/swiftnodes. Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key. This page covers its hosted endpoint (https://rpc.swiftnodes.io/mcp).

### Is the SwiftNodes RPC MCP server safe to use?

SwiftNodes RPC scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SwiftNodes RPC MCP server expose?

SwiftNodes RPC exposes 7 tools: list_chains, get_chain, get_pricing, get_method_support, probe_endpoint, and 2 more. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.

### Does the SwiftNodes RPC MCP server require authentication?

No. We connected to SwiftNodes RPC without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SwiftNodes RPC MCP server still maintained?

SwiftNodes RPC is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://rpc.swiftnodes.io/mcp
- Repository: https://github.com/swiftnodes/swiftnodes-mcp
- Website: https://swiftnodes.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/rpc.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/rpc.json
- HTML version of this page: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/rpc