Skip to content

SwiftNodes RPC MCP server

io.swiftnodes/swiftnodesswiftnodes.iostreamable-httpv1.0.1Scanned

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

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 7
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SwiftNodes RPC MCP server can do

The SwiftNodes RPC MCP server is published by swiftnodes.io, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: probe_endpoint and rpc_call), but cannot delete data. 5 tools only read.

7 tools bring in text other people can write (list_chains, get_chain, get_pricing and 4 more); 1 tool can send data out of your system (probe_endpoint).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 2Claude Code: ask
  • probe_endpointDiagnose any public EVM JSON-RPC endpoint.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • rpc_callMake a JSON-RPC call on any SwiftNodes chain with the caller's API key (sent to this MCP server as 'Authorization: Bearer <key>').Reads text others write1 finding

    Why it is in this group

    • The name "rpc_call" says "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "rpc_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "rpc_call" says "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • get_accountThe caller's SwiftNodes plan, rate limits, requests used this month, and the IP/origin restrictions on the key in use.Reads text others writeNo findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_chainOne chain in detail: chain ID, live status and block height, and the HTTP, WebSocket and archive endpoint URL templates.Reads text others writeNo findings

    Why it is in this group

    • The name "get_chain" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One chain in detail: chain ID, live status and block height, and the HTTP, WebSocket and archive endpoint URL templates.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_method_supportWhich JSON-RPC methods work on which chain, probed weekly through the customer request path.Reads text others writeNo findings

    Why it is in this group

    • The name "get_method_support" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_pricingSwiftNodes plans: flat monthly price, HTTP and WebSocket rate limits.Reads text others writeNo findings

    Why it is in this group

    • The name "get_pricing" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    SwiftNodes plans: flat monthly price, HTTP and WebSocket rate limits. No compute units, no per-request billing.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_chainsList every blockchain SwiftNodes serves (one API key for all): name, slug, chain ID, live status, and whether WebSocket and archive (?archive=1) are available.Reads text others writeNo findings

    Why it is in this group

    • The name "list_chains" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:14 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rpc.swiftnodes.io/mcp: tools/list returned 7 tools to an anonymous client, including probe_endpoint (write), rpc_call (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "rpc_call" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "rpc_call" says "call": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__swiftnodes__list_chains",
      "mcp__swiftnodes__get_chain",
      "mcp__swiftnodes__get_pricing",
      "mcp__swiftnodes__get_method_support",
      "mcp__swiftnodes__get_account"
    ],
    "ask": [
      "mcp__swiftnodes__probe_endpoint",
      "mcp__swiftnodes__rpc_call"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as swiftnodes. Review it before you use it.

Capability tags behind 7 rules
  • mcp__swiftnodes__list_chains untrusted-input
  • mcp__swiftnodes__get_chain untrusted-input
  • mcp__swiftnodes__get_pricing untrusted-input
  • mcp__swiftnodes__get_method_support untrusted-input
  • mcp__swiftnodes__probe_endpoint untrusted-input, outbound
  • mcp__swiftnodes__rpc_call untrusted-input
  • mcp__swiftnodes__get_account untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.swiftnodes/swiftnodes/verify?hash=f9b097d0d5c0be7077317066f23464dab36f5afb771e5db01fadb23dfa477cc6" | jq -e '.changed == false'

Pinned hash f9b097d0d5c0, from Nov 17, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.swiftnodes/swiftnodes/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.swiftnodes/swiftnodes
[![Anlyon Radar](https://radar.anlyon.com/badge/io.swiftnodes/swiftnodes.svg)](https://radar.anlyon.com/servers/io.swiftnodes/swiftnodes)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.

SwiftNodes RPC MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SwiftNodes RPC MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SwiftNodes RPC MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SwiftNodes RPC MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SwiftNodes RPC MCP server have?

7 tools: 2 write, 5 read. probe_endpoint, rpc_call, list_chains, get_chain, get_pricing, get_method_support and get_account.

Does the SwiftNodes RPC MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SwiftNodes RPC MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): probe_endpoint.

Has the SwiftNodes RPC MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.