SwiftNodes RPC
Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'get_method_support' description lacks action verbin get_method_support
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"swiftnodes": {
"command": "npx",
"args": [
"swiftnodes-mcp"
]
}
}
}Runnable packages
0.2.0stdioRemote endpoints
https://rpc.swiftnodes.io/mcpstreamable-httpWhat it can do
Tool inventory
Tools (7)
🟢list_chains(query, evm_only)
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 Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Optional name or slug filter, e.g. 'base' or 'zksync'."
},
"evm_only": {
"type": "boolean",
"description": "Only EVM chains."
}
}
}🟢get_chain(chain)
One chain in detail: chain ID, live status and block height, and the HTTP, WebSocket and archive endpoint URL templates.
Input Schema
{
"type": "object",
"properties": {
"chain": {
"type": "string",
"description": "Chain slug, name or chain ID, e.g. \"eth\", \"Base\", \"4663\"."
}
},
"required": [
"chain"
]
}🟢get_pricing
SwiftNodes plans: flat monthly price, HTTP and WebSocket rate limits. No compute units, no per-request billing.
Input Schema
{
"type": "object",
"properties": {}
}🟢get_method_support(method)
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 Schema
{
"type": "object",
"properties": {
"method": {
"type": "string",
"description": "e.g. 'trace_filter' or 'eth_getProof'."
}
}
}🟢probe_endpoint(url, method, params)
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 Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "Public http(s) RPC URL."
},
"method": {
"type": "string"
},
"params": {
"type": "array"
}
},
"required": [
"url"
]
}🟢rpc_call(chain, method, params, archive)
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 Schema
{
"type": "object",
"properties": {
"chain": {
"type": "string",
"description": "Chain slug, e.g. \"eth\", \"base\", \"robinhood\". See list_chains."
},
"method": {
"type": "string",
"description": "e.g. \"eth_blockNumber\"."
},
"params": {
"type": "array",
"description": "Method params, default []."
},
"archive": {
"type": "boolean",
"description": "Route to archive upstreams (paid plans)."
}
},
"required": [
"chain",
"method"
]
}🟢get_account
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
{
"type": "object",
"properties": {}
}Community
Evidence