swiftnodes-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_chainsA | List every blockchain SwiftNodes serves (75+ 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. |
| get_chainA | Full details for one chain SwiftNodes serves: chain ID, category, block time, native currency, HTTP/WebSocket/archive endpoint URL templates, and docs links. |
| get_pricingA | Live flat-rate pricing for SwiftNodes RPC: monthly plans, HTTP/WS rate limits, included features. No per-request fees or compute units. |
| get_method_supportA | 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. |
| probe_endpointA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: listing chains, fetching one chain's details, getting pricing, checking method support, and probing arbitrary endpoints. No two tools overlap in a way that would cause an agent to select the wrong one.
All tool names follow a consistent snake_case verb_noun pattern: list_chains, get_pricing, get_chain, get_method_support, probe_endpoint. The verbs and nouns are predictable and match the action each tool performs.
Five tools is well-scoped for this server's purpose: catalog discovery, detail lookup, pricing, capability checking, and endpoint diagnostic. Each tool earns its place and there is no bloat.
The domain is SwiftNodes' chain and RPC support surface, and the tools cover discovery, detail, pricing, method compatibility, and live diagnosis. There are no obvious dead ends or critical missing operations for the stated purpose.