Paper copy-watch
doctor → logsSubscribe one wallet → paper log. For copy-trading bots.
git clone https://github.com/rpc-edge/rpcedge-copy-ref.git cd rpcedge-copy-ref && pnpm install export RPCEDGE_KEY=your-uuid-key pnpm doctor && pnpm start
◆ SDK · CLI · MCP
Ship Solana bots without endpoint guesswork.
Open MIT DX for rpc edge: prove a key, wire TypeScript, hand tools to Claude and Cursor - then paper copy-watch or DLMM pool-watch for first real traffic (no auto-trade).
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 → doctor → first slot
3 surfaces
CLI, TypeScript, MCP
Paper refs
copy-watch · DLMM pool-watch
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 ↓First traffic
Paper refs for wallet or DLMM pool streams - then SDK/MCP for your strategy.
Paper paths ↓
export RPCEDGE_KEY=your-uuid-key npx rpcedge@latest doctor npx rpcedge@latest health --json
// last updated 2026-08-13 · public demo path works without a key; production needs RPCEDGE_KEY
◆ AFTER DOCTOR GREEN
First traffic, paper only.
Separate MIT repos. Prove the wire with real chain activity - no auto-trade, no rebalance, no private keys in the ref. Strategy stays yours.
Paper DLMM pool-watch
doctor → accountSubscribe a Meteora Lb pool → paper log. For DLMM bots.
git clone https://github.com/rpc-edge/rpcedge-dlmm-ref.git cd rpcedge-dlmm-ref && pnpm install export RPCEDGE_KEY=your-uuid-key # optional: export WATCH_POOL=<your Meteora Lb pool> pnpm doctor && pnpm start
Pick how you ship.
Same core, three surfaces. Start with doctor, then stay on the path that matches your stack.
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
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 # first traffic (paper only - not strategies) # git clone https://github.com/rpc-edge/rpcedge-copy-ref && cd rpcedge-copy-ref && pnpm i && pnpm start # git clone https://github.com/rpc-edge/rpcedge-dlmm-ref && cd rpcedge-dlmm-ref && pnpm i && pnpm start
Machine guide: /skills.md. Agents discovery: /agents.
Straight answers.
Is the toolkit free?
Yes - MIT on npm and GitHub (rpcedge, rpcedge-sdk, rpcedge-mcp). Every account can create one API key on the permanent Free plan. Doctor can hit public mainnet without a key for a demo path; rpc edge endpoints use 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. Paper refs (copy-ref, dlmm-ref) sit next door for first real traffic without a strategy bot.
How do I get a key?
Sign up at app.rpcedge.com and create your Free API key, then export RPCEDGE_KEY and run npx rpcedge doctor. Upgrade to Beginner, Trader, or Desk from Billing when you need more capacity or streaming.
What is the fastest path to first traffic?
1) npx rpcedge doctor green. 2) Paper path: rpcedge-copy-ref (wallet logsSubscribe) or rpcedge-dlmm-ref (Meteora pool accountSubscribe). Both log only - no auto-trade or rebalance. 3) Build strategy on SDK/MCP when the wire is proven.
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. Paper refs do not claim co-lo hero numbers either.
Is there a copy-trading or DLMM bot in the toolkit?
No auto-trader and no rebalancer. Separate MIT paper refs: github.com/rpc-edge/rpcedge-copy-ref (wallet watch) and github.com/rpc-edge/rpcedge-dlmm-ref (pool accountSubscribe). Wiring only - not strategies.
Which packages do I install?
rpcedge (CLI), rpcedge-sdk (TypeScript), rpcedge-mcp (stdio MCP). Monorepo: github.com/rpc-edge/rpcedge-toolkit. Provider-agnostic MCP twin: solana-infra-mcp.
Get a key. Run doctor. Ship.
Self-serve from $49/mo USDC. Co-located Solana infra for trading bots - toolkit is the open door. Paper refs prove traffic; you own strategy and keys.
// source github.com/rpc-edge/rpcedge-toolkit