gasrescue
Rescue USDC, USDT and USDG from wallets with no gas: send or swap them on EVM, Solana and Tron.
Description from the maker (original English)
Blockchain RPC for 125+ chains: endpoints, method support, probing and RPC calls with your key.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"swiftnodes": {
"command": "npx",
"args": [
"-y",
"swiftnodes-mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http swiftnodes https://rpc.swiftnodes.io/mcp --header 'Authorization: your-value'claude mcp add swiftnodes -- npx -y swiftnodes-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"swiftnodes": {
"url": "https://rpc.swiftnodes.io/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"swiftnodes": {
"command": "npx",
"args": [
"-y",
"swiftnodes-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"swiftnodes": {
"type": "http",
"url": "https://rpc.swiftnodes.io/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"swiftnodes": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"swiftnodes-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.
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.
get_chainOne chain in detail: chain ID, live status and block height, and the HTTP, WebSocket and archive endpoint URL templates.
get_pricingSwiftNodes plans: flat monthly price, HTTP and WebSocket rate limits. No compute units, no per-request billing.
get_method_supportWhich 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.
probe_endpointDiagnose 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.
rpc_callMake a JSON-RPC call on any SwiftNodes chain with the caller's API key (sent to this MCP server as 'Authorization: Bearer '). Counts against that key's plan like any other request. Read-only: methods that send or sign transactions are refused.
get_accountThe caller's SwiftNodes plan, rate limits, requests used this month, and the IP/origin restrictions on the key in use. Needs 'Authorization: Bearer '. Never returns key values.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified against the domain swiftnodes.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 523 ms (HTTP 200)
No sign-in needed
Read 7 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: gasrescue, xsolana, CashPan
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Rescue USDC, USDT and USDG from wallets with no gas: send or swap them on EVM, Solana and Tron.
Design, check, simulate and launch Solana game economies on loot, one shared program, no contract.
Give your AI an allowance: pay approved people within on-chain spending limits.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP (Model Context Protocol) server for SwiftNodes — multi-chain blockchain RPC, exposed to AI agents.
One API key, 125+ chains, flat-rate pricing. This server gives Claude, ChatGPT, Cursor, and any MCP client live, factual answers about chains, pricing, and JSON-RPC method support — plus the ability to probe any EVM endpoint directly.
Works across all 128 SwiftNodes chains, including Ethereum, BNB Smart Chain (BSC), opBNB, Base, Arbitrum, Polygon, Solana and Bitcoin. Each chain has a slug used in tool arguments and endpoint URLs, for example:
| Chain | Slug | Endpoint |
|---|---|---|
| BNB Smart Chain (BSC) | bsc | https://rpc.swiftnodes.io/rpc/bsc?key=YOUR_API_KEY |
| opBNB | opbnb | https://rpc.swiftnodes.io/rpc/opbnb?key=YOUR_API_KEY |
| Ethereum | eth | https://rpc.swiftnodes.io/rpc/eth?key=YOUR_API_KEY |
| Base | base | https://rpc.swiftnodes.io/rpc/base?key=YOUR_API_KEY |
Example prompts: "Which JSON-RPC methods does BNB Smart Chain support?", "What is the latest block on opBNB?", "Is trace_filter available on BSC?". list_chains returns the full list.
SwiftNodes runs this server for you at `https://rpc.swiftnodes.io/mcp` (Streamable HTTP). Nothing to install.
claude mcp add --transport http --scope user swiftnodes https://rpc.swiftnodes.io/mcp --header "Authorization: Bearer $SWIFTNODES_API_KEY"
Cursor and other clients (~/.cursor/mcp.json):
{ "mcpServers": { "swiftnodes": { "url": "https://rpc.swiftnodes.io/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
The key is optional: without it the public tools below work. With it, two more tools are available:
| Tool | What it does |
|---|---|
rpc_call | Make a JSON-RPC call on any SwiftNodes chain with your key (counts against your plan like any request). |
get_account | Your plan, rate limits, requests used this month, and the IP/origin restrictions on the key. Never returns key values. |
Listed in the official MCP Registry as io.swiftnodes/swiftnodes. Docs: https://swiftnodes.io/docs/mcp
| Tool | What it does |
|---|---|
list_chains | Every chain SwiftNodes serves — name, slug, chain ID, category, docs page. Filterable. |
get_chain | Full detail for one chain: IDs, block time, native currency, HTTP/WebSocket/archive endpoint templates, docs links. |
get_pricing | Live flat-rate plans from the public API — rate limits, included features, no compute units. |
get_method_support | Which JSON-RPC methods work on which chain — auto-probed weekly through the same path customer requests take. Overview or per-method detail. |
probe_endpoint | Diagnose any EVM JSON-RPC endpoint (ours or anyone's): chain identity, block height, archive capability, latency — or run a specific method call. |
Zero dependencies, Node >= 18.
From this repo:
git clone https://github.com/swiftnodes/swiftnodes-mcp
node swiftnodes-mcp/bin/server.js # speaks MCP over stdio
Via npm (once published): npx -y swiftnodes-mcp
{
"mcpServers": { "swiftnodes": { "command": "node", "args": ["/path/to/swiftnodes-mcp/bin/server.js"] } } }
Add a stdio server with command node and args ["/path/to/swiftnodes-mcp/bin/server.js"].
scripts/generate-chains-data.mjs; regenerate after chain changes).https://rpc.swiftnodes.io/api/plans (bundled fallback if unreachable).https://swiftnodes.io/method-matrix.json, re-probed weekly. Support values reflect the real customer path, including failover.probe_endpoint will call any http(s) URL you give it — the same ground our CLI diagnostic rpc-doctor covers. Probe responsibly: one quick pass per endpoint, not a load test.
Questions: swiftnodes.io — free tier, no KYC.
MIT — see LICENSE.