What does this skill do, and when should you use it?
drpc-rpc is one of the two skills bundled in drpcorg/drpc-agent-skills (MIT licensed). It gives AI coding agents blockchain access through the DRPC decentralized RPC gateway, spanning 100+ blockchains and 200+ networks. On first use it acquires an API key automatically via the x402 protocol when the agent has an EVM wallet (free via SIWE sign-in, 5 USDC for new wallets), falling back to asking the user. The current request executes immediately over direct HTTP while MCP is configured for future sessions. It ships recipes for single-network queries, cross-chain comparisons, DeFi protocols (Aave, Uniswap, Lido, etc.), client selection, and error-code diagnostics.
- Detects whether DRPC MCP tools are already available and uses them directly (eth_getBalance, eth_call, rpc_call, etc.)
- Auto-acquires an API key via x402: free SIWE wallet sign-in, or EIP-3009 USDC payment on Base for new wallets
- Falls back to asking the user for a DRPC key or pointing to the free tier at drpc.org
- Executes the current request immediately over direct HTTP (no restart) and configures MCP for future sessions
- Routes queries to reference docs: single-network, cross-chain, DeFi basics and protocols, client selection (reth/geth/erigon), error handling
- Reaches non-EVM chains (Solana, Bitcoin, NEAR, Cosmos) via rpc_call and batches same-network queries with rpc_batch
- A DeFi user who wants wallet balances and holdings across Ethereum, Arbitrum and Base via plain English prompts
- A developer who needs to read on-chain contract data (e.g. USDC totalSupply on Base) without hand-writing curl calls or running a node
- An analyst comparing current gas prices across L2s or checking whether a transaction is confirmed on Optimism
- An agent user with an EVM wallet who wants zero-signup API key acquisition and instant first query
- An on-chain researcher tracking recent transactions of an address (whale watching) or querying event logs
- Users who won't grant network access or a wallet, and don't want to obtain an API key — every query path requires a DRPC key
- Scenarios needing to send transactions or perform on-chain writes — the skill covers read-only RPC only (balances, blocks, logs, eth_call)
- Offline or sandboxed agents that cannot make HTTP/MCP calls — both key acquisition and data queries depend on the network
How do you install this skill?
- The x402 flow signs with an EVM wallet the agent can access and may pay 5 USDC (EIP-3009, settled on Base); confirm wallet permission scope before use and consider disabling the auto-payment step.
- API keys are passed in URL paths and may appear in shell history, proxies, or server logs; read keys from environment variables and avoid logging full URLs as the docs suggest.
- This review is static source reading only; no calls were executed. Endpoint formats, SSE responses and error codes are unverified by testing.
- Core function depends entirely on overseas services (lb.drpc.org, drpc.org) and USDC payment on Base; mainland-China network reachability is undeclared and may be unstable.
- Example outputs (balances, gas prices, DeFi positions) are illustrative fabricated data; verify real results independently.
- Publisher is not verified by the FollowSkills curated registry; identity is treated as unknown.
- Shell / CLI
- Network access
- Local filesystem
- MCP Server
DRPC API key (or EVM wallet for x402 auto-key)MCP server for persistent sessions
Install the skill collection; this skill lives at skills/drpc-rpc/. Per-platform commands:
Claude Code
claude plugins marketplace add drpcorg/drpc-agent-skills
claude plugins install drpc-agent-skillsGemini CLI
gemini extensions install https://github.com/drpcorg/drpc-agent-skillsCodex
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc ~/.agents/skills/drpc-rpcPi Agent
pi install npm:pi-mcp-adapter
pi install https://github.com/drpcorg/drpc-agent-skillsCursor
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .cursor/skills/drpc-rpcWindsurf
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .windsurf/skills/drpc-rpcCline
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc .cline/skills/drpc-rpcOpenClaw
git clone https://github.com/drpcorg/drpc-agent-skills.git
ln -s $(pwd)/drpc-agent-skills/skills/drpc-rpc ~/.openclaw/skills/drpc-rpcHow do you use this skill?
Once installed, send your agent any of these to trigger it:
- Get the ETH balance of vitalik.eth on Ethereum
- Compare gas prices across all L2 networks right now
- Check if transaction 0xabc... is confirmed on Optimism
- Read the totalSupply of the USDC contract on Base
The skill triggers on natural-language requests for blockchain data (balances, transactions, blocks, gas, contract reads) or mentions of DRPC, Web3, Ethereum RPC, or method names like eth_getBalance. Flow: (1) detect if MCP tools are available; (2) if not, auto-acquire a key via x402 — SIWE sign-in is free for linked wallets, new wallets pay 5 USDC via EIP-3009 on Base; (3) without a wallet, ask the user for a key or direct them to drpc.org's free tier; (4) execute the current request immediately via direct HTTP and configure MCP for future sessions; (5) route by query type to the matching recipe file. Useful options: run list_networks first when unsure of network names; use rpc_batch for multiple queries on one network; rpc_call for non-EVM chains; client-selection.md for routing to reth/geth/erigon; check errors.md on failures (HTTP 429 = rate limited, retry after 1-2s; 403 = billing/auth).
What are this skill's strengths and limitations?
- Works on first ask: no restart or manual config-file editing; the request executes immediately after key acquisition
- Wallet-holding agents get a key automatically via x402 with no signup; all signatures are off-chain with no user gas
- Requests route through DRPC's decentralized gateway with consensus validation, avoiding bad data from a single node
- Broad coverage: 200+ networks, 16 MCP tools, including non-EVM chains (Solana, Bitcoin, NEAR, Cosmos)
- Well-documented: parameter reference for all 16 tools, scenario-organized recipes, error codes and recovery patterns
- Every query depends on the DRPC service and an API key; the new-wallet x402 path costs 5 USDC, so there is an ongoing billing relationship
- Read-only RPC coverage — no transaction sending or on-chain writes
- Platform compatibility claims (8 hosts in the README) are self-reported without independent test evidence
- The x402 auto-key flow requires the agent to hold an EVM wallet private key/signer — a significant security-sensitive prerequisite
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| DRPC Blockchain RPC Skill this page | 50 · Use with care | ★ 23 | 4mo ago | MIT |
| DRPC RPC — Pi Agent Setup Overlay | 50 · Use with care | ★ 23 | 4mo ago | MIT |
| GitHub Copilot SDK Builder ✓ Microsoft · Official | 49 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Contracts Engine Verifier ✓ Anthropic · Official | 44 · Not recommended | ★ 425 | 1mo ago | — |
| Stitch React Dashboard Builder | 40 · Not recommended | ★ 8.5k | 2mo ago | Apache-2.0 |
Compared to manually configuring an RPC node or curling public endpoints, this skill removes method selection, format debugging and key management, at the cost of being bound to the DRPC gateway and its pricing. Compared to a plain single-node RPC MCP server, it adds decentralized multi-provider routing, consensus-validated responses, and execution-client selection (reth/geth/erigon). The source names no other specific competitors.
How did FollowSkills review this skill?
Data flow is transparently disclosed: API key acquisition, x402 wallet signing and on-chain USDC payment are all documented with a manual fallback (user-supplied key). No hard-coded secrets; repeated warnings not to leak keys. Deductions: Step 2 lets the agent automatically sign with the user's EVM wallet and pay 5 USDC without an explicit user-confirmation gate; API keys sit in URL paths and may leak into logs; publisher unverified, update/revocation path unclear. Not a red line, but authorization/confirmation is incomplete.
Files are internally consistent: transport detection, direct HTTP, the error-code table and recovery patterns interlock; failure feedback is detailed (HTTP codes, DRPC codes, actions) and explains why it cannot proceed. Deductions: static review only — endpoint behavior, SSE format and the x402 flow are unverified; no test suite or committed reproduction evidence; the x402 auto-key critical path especially depends on unverified external services.
Trigger conditions are specific (eth_getBalance, DRPC, Web3, etc.), scenarios are clear (balances, transactions, cross-chain, DeFi), and capability boundaries are stated (client selection is a routing hint, not machine pinning). Deductions: core function depends entirely on overseas services (lb.drpc.org, drpc.org, USDC on Base) with no mainland-China reachability statement; no Chinese support; non-fit ranges only partially declared.
Good layered information architecture (entry point → routing by query type to topic files), install instructions across 8 platforms, clear MIT license, maintenance by the drpcorg org. Deductions: version is only 0.1.0 with no changelog; tools-reference.md and x402-auto-key.md were not provided in this review so referenced completeness cannot be confirmed; known-limitation disclosure is scattered.
Recipes (balance, gas comparison, Aave/Uniswap positions, etc.) come with concrete curls and selectors and claim directly presentable tabular output; marginal value is clear (avoids hand-writing RPC boilerplate). Deductions: under static review direct usability is unconfirmed; example outputs are illustrative, not verified results; some sample data (gas table) is clearly fabricated snapshots.
Substantial auditable primary material is present: complete curl commands, function selectors, real contract addresses, error-code tables enabling independent reproduction. Deductions: no execution evidence, no CI workflows or committed tests covering key paths; claims like '200+ networks' link only to an external site unverifiable in-repo; example outputs are uncorroborated.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →