Prove the key
Shell and CI. Doctor checks auth and health; fees and leaders for the trading loop; send signed txs via the relay.
export RPCEDGE_KEY=your-uuid-key npx rpcedge@latest doctor npx rpcedge@latest fee npx rpcedge@latest grpc-sample
◆ SDK · CLI · MCP
Ship Solana bots without endpoint guesswork.
Open MIT toolkit: prove a key, wire TypeScript, hand live tools to Claude and Cursor.
export RPCEDGE_KEY=your-uuid-key npx rpcedge@latest doctor npx rpcedge@latest health --json
// measures from this host - not a co-located landing claim
MIT
Open source on npm and GitHub
60s
Key to doctor to first slot
3 surfaces
CLI, TypeScript, MCP
Honest
Physics over promises
The setup you already hate.
Without
With toolkit
Paste a URL, forget WS, mis-auth gRPC
npx rpcedge doctor proves the key
Re-implement fee percentiles and leaders
CLI, MCP, and SDK share one core
Agent invents curl in the prompt
MCP tools with env-held keys only
Send to public RPC and hope
send --raw / relay submit path
Three steps to first green.
Get a key
Sign up, pay USDC, mint a UUID key in the dashboard.
Open signup →Run doctor
Export RPCEDGE_KEY and prove auth + health before bot code.
Copy command ↓Ship traffic
SDK for bots, MCP for agents, relay for signed submits.
Docs quickstart →
export RPCEDGE_KEY=your-uuid-key npx rpcedge@latest doctor npx rpcedge@latest health --json
// last updated 2026-07-31 · public demo path works without a key; production needs RPCEDGE_KEY
Pick how you ship.
Same core, three surfaces. Start with doctor, then stay on the path that matches your stack.
Wire the bot
TypeScript: fromEnv, getSlot, health, priority fees, Connection helper, relay submit. No raw URL string glue.
pnpm add rpcedge-sdk
import { RpcEdge } from "rpcedge-sdk";
const edge = await RpcEdge.fromEnv();
console.log(await edge.getSlot());Hand tools to agents
Claude Code, Cursor, Codex. Doctor, fees, leaders, Yellowstone sample, relay submit. Keys stay in env, never in prompts.
export RPCEDGE_KEY=your-uuid-key claude mcp add rpcedge -- npx rpcedge-mcp@latest # ask: check my RPC health and priority fees
What agents can call.
Branded server rpcedge-mcp. Signing is always upstream. Provider-agnostic twin: solana-infra-mcp.
doctorKey + health checklist with next actionsrpc_healthSlot, solana-core, getSlot RTT (this host)priority_fee_estimatep50/p75/p90/max micro-lamports per CUepoch_infoEpoch progress and block heightnext_leadersNext N slot leaders for timinglatency_comparegetSlot p50 vs baseline - not landingyellowstone_sampleTime-boxed gRPC slot sample (needs key)submit_transactionSigned base64 tx via relay + confirmendpoint_mapCanonical endpoints + auth (no secrets)// rpc_health · priority_fee_estimate · epoch_info · next_leaders · latency_compare · submit_transaction · doctor · endpoint_map · yellowstone_sample
export RPCEDGE_KEY=your-uuid-key claude mcp add rpcedge -- npx rpcedge-mcp@latest
Full stack in one block.
export RPCEDGE_KEY=your-uuid-key # prove the key npx rpcedge@latest doctor # TypeScript bot pnpm add rpcedge-sdk # coding agent claude mcp add rpcedge -- npx rpcedge-mcp@latest
Machine guide: /skills.md. Agents discovery: /agents.
Straight answers.
Is the toolkit free?
Yes - MIT on npm and GitHub. Production rpc edge endpoints still need a paid plan and API key. Doctor can hit public mainnet without a key for a demo path; production uses RPCEDGE_KEY.
How is this different from /tools?
/tools is browser utilities with no key (priority fee estimator). /toolkit is the install surface for bots and coding agents: CLI, TypeScript SDK, and MCP.
How do I get a key?
Sign up at app.rpcedge.com, choose Trader or Desk, pay in USDC on Solana, create an API key, export RPCEDGE_KEY, then run npx rpcedge doctor.
Can agents use it without putting keys in prompts?
Yes. Set RPCEDGE_KEY in the host process or MCP env. Tools redact hosts and never echo the secret. Submit tools accept only fully signed base64 transactions.
What about Yellowstone / streams?
Use yellowstone_sample (MCP) or rpcedge grpc-sample (CLI) for a time-boxed slot probe. For production, wire any Yellowstone client to grpc.rpcedge.com:443 with x-api-key metadata. Long-lived streams stay in your bot - not in MCP.
Do you invent latency numbers?
No. Doctor and latency tools measure from your machine. For co-located first-seen and landing metrics, run solbench on the edge - physics over promises.
Get a key. Run doctor. Ship.
Self-serve from $249/mo USDC. Co-located Solana infra for trading bots - toolkit is the open door.
// source github.com/rpc-edge/rpcedge-toolkit