SwiftNodes RPC
REMOTE · RPC.SWIFTNODES.IO · 2 COMPONENTS
Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.
Available components
Last scanned (11 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 570 tokens (~81/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://rpc.swiftnodes.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rpc.swiftnodes.io | CN=YE1,O=Let's Encrypt,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f0d032c75a30a019a052903781fa1c4f81 |
| SANs: rpc.swiftnodes.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rpc.swiftnodes.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| swiftnodes.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rpc.swiftnodes.io/mcp | Verified | 200 | |
| http (plaintext) | http://rpc.swiftnodes.io/mcp | HTTPS enforced | 301 | https://rpc.swiftnodes.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_account ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_chain ~61
One chain in detail: chain ID, live status and block height, and the HTTP, WebSocket and archive endpoint URL templates.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain slug, name or chain ID, e.g. "eth", "Base", "4663". |
No output schema declared.
No examples provided.
get_method_support ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | e.g. 'trace_filter' or 'eth_getProof'. |
No output schema declared.
No examples provided.
get_pricing ~33
SwiftNodes plans: flat monthly price, HTTP and WebSocket rate limits. No compute units, no per-request billing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_chains ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| evm_only | boolean | – | Only EVM chains. |
| query | string | – | Optional name or slug filter, e.g. 'base' or 'zksync'. |
No output schema declared.
No examples provided.
probe_endpoint ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | – |
| params | array | – | – |
| url | string | yes | Public http(s) RPC URL. |
No output schema declared.
No examples provided.
rpc_call ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archive | boolean | – | Route to archive upstreams (paid plans). |
| chain | string | yes | Chain slug, e.g. "eth", "base", "robinhood". See list_chains. |
| method | string | yes | e.g. "eth_blockNumber". |
| params | array | – | Method params, default []. |
No output schema declared.
No examples provided.
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.
remote · rpc.swiftnodes.io
claude mcp add --transport http io-swiftnodes-swiftnodes 'https://rpc.swiftnodes.io/mcp'
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.