Every one of these calls is something you could make yourself with an RPC URL and a curl line; what the pack adds is that the agent knows which method answers the question, which network to ask it on, and what to do when the reply is a billing error rather than a block. The consensus-validated gateway is the other half of it — a wrong answer from a single node is the failure that is hardest to notice.
DRPC's own skill pack, which points a coding agent at DRPC's hosted JSON-RPC gateway and teaches it which call answers which question. Requests are routed across several node providers and the responses are consensus-validated, so one provider going down — or returning something wrong — does not quietly become your answer. The pack carries install steps for eight agent clients, recipes for single-network and cross-chain questions, a client-selection guide, and an error guide covering billing limits and rate limiting. An agent that holds a wallet can obtain the API key by signing rather than by signing up; otherwise you paste a free key from drpc.org.
- The supported networks listed, and the RPC methods available on any one of them
- A network's own details — chain id, native currency, block explorers
- Native token balance for an address, on any network in the list
- A block by number or tag, or by hash
- A transaction by hash, and its receipt with status and logs
- Event log queries, and read-only contract calls
- Current gas price, and a gas estimate for a call you are about to make
- Contract bytecode at an address, and an address's transaction count
- Any JSON-RPC method a network supports, and batches of them in one round trip
One command plus a key — claude mcp add --transport http drpc https://lb.drpc.org/mcp/API_KEY, then supply credentials