# SwiftNodes RPC (npm · swiftnodes-mcp)

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

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `swiftnodes-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 450 tokens (~90/item across 5 items; 5 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

SwiftNodes RPC runs locally as an npm package, launched with npx -y swiftnodes-mcp. 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 io-swiftnodes-swiftnodes -- npx -y swiftnodes-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-swiftnodes-swiftnodes": {
      "command": "npx",
      "args": [
        "-y",
        "swiftnodes-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-swiftnodes-swiftnodes": {
      "command": "npx",
      "args": [
        "-y",
        "swiftnodes-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-swiftnodes-swiftnodes -- npx -y swiftnodes-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-swiftnodes-swiftnodes": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "swiftnodes-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-swiftnodes-swiftnodes --command npx --arg -y --arg swiftnodes-mcp
```

### Hermes

```yaml
mcp_servers:
  io-swiftnodes-swiftnodes:
    command: "npx"
    args: ["-y", "swiftnodes-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-swiftnodes-swiftnodes": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "swiftnodes-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-swiftnodes-swiftnodes -t stdio -c npx -a -y swiftnodes-mcp
```

### Other

```json
{
  "mcpServers": {
    "io-swiftnodes-swiftnodes": {
      "command": "npx",
      "args": [
        "-y",
        "swiftnodes-mcp"
      ]
    }
  }
}
```

## 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-23 (score 74, +4)

- [functional improvement] Stability: unverified → 0.27

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

First indexed and scored.

## MCP tools (5)

### `list_chains` (~97 tokens)

List every blockchain SwiftNodes serves (125+ chains, one API key for all). Returns name, slug, chain ID, category, and docs page per chain. Use before get_chain if unsure of the exact chain name.

Input parameters:

- `evm_only` (boolean): If true, only EVM chains are returned.
- `query` (string): Optional name/slug substring filter, e.g. 'base' or 'zksync'.

### `get_chain` (~65 tokens)

Full details for one chain SwiftNodes serves: chain ID, category, block time, native currency, HTTP/WebSocket/archive endpoint URL templates, and docs links.

Input parameters:

- `chain` (string, required): Chain name or slug, e.g. 'Ethereum', 'base', 'zksync'.

### `get_pricing` (~38 tokens)

Live flat-rate pricing for SwiftNodes RPC: monthly plans, HTTP/WS rate limits, included features. No per-request fees or compute units.

### `get_method_support` (~86 tokens)

Which JSON-RPC methods work on which chain, auto-probed weekly through the real customer path (eth_getProof, trace_block, trace_filter, batching, archive, and more). Call with no args for the overview, or {method} for per-chain support.

Input parameters:

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

### `probe_endpoint` (~115 tokens)

Diagnose ANY EVM JSON-RPC endpoint (ours or anyone's). With {url} only: checks chain identity, block height, and archive capability with latency. With {url, method, params}: performs that exact JSON-RPC call and returns the result or error.

Input parameters:

- `method` (string): Optional JSON-RPC method to call, e.g. 'eth_chainId'.
- `params` (array): Optional params array for the method call.
- `url` (string, required): The http(s) RPC endpoint URL to probe.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/swiftnodes-mcp#diagnostics

## Score history

- 2026-10-23: 74
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 70
- 2026-10-16: 70
- 2026-10-15: 70

## 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 npm package (swiftnodes-mcp).

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

SwiftNodes RPC scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. 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 5 tools: list_chains, get_chain, get_pricing, get_method_support, probe_endpoint. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.

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

### What licence is the SwiftNodes RPC MCP server under?

SwiftNodes RPC declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/swiftnodes-mcp
- Socket report: https://socket.dev/npm/package/swiftnodes-mcp
- Repository: https://github.com/swiftnodes/swiftnodes-mcp
- Website: https://swiftnodes.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/swiftnodes-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/swiftnodes-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-swiftnodes-swiftnodes/swiftnodes-mcp