What does this skill do, and when should you use it?
This is a Pi Agent-specific setup overlay skill, one of two skills bundled in the drpc-agent-skills repository. When the user asks for blockchain data but DRPC MCP is not configured, it runs a bootstrap flow: it installs and calls the Coinbase Payments MCP, acquires a DRPC API key via the x402 protocol, and writes the key into ~/.pi/agent/mcp. to configure DRPC MCP. It exposes two agent-callable tools, drpc_setup and drpc_coinbase_wallet_setup, plus two manual slash commands. Security is a core design point: it never asks the user for private keys, keeping wallet custody outside Pi via the Coinbase Agentic Wallet.
- Checks the MCP server list in the current Pi session to see if DRPC MCP is available
- Calls drpc_setup without an apiKey to install and configure Coinbase Payments MCP, writing to ~/.pi/agent/mcp.
- Uses payments-mcp to acquire a DRPC API key via x402
- Calls drpc_setup again with the acquired key to configure DRPC MCP in Pi
- Tells the user to reload or restart the Pi/MCP session when a newly written MCP server is not yet visible
- Falls back to the direct HTTP method in skills/drpc-rpc/direct-http.md if DRPC MCP remains unavailable
- A Pi Agent user requesting on-chain data without DRPC configured, who wants the agent to bootstrap setup instead of hand-editing config files
- A developer with an on-chain wallet who wants an API key acquired automatically via x402 without signup
- A security-conscious team that wants wallet custody handled by the Coinbase Agentic Wallet outside Pi
- A user whose newly written MCP server is not visible and needs to know when and why to restart the Pi/MCP session
- Users on non-Pi platforms such as Claude Code or Cursor — this skill explicitly scopes itself to Pi Agent with the repo installed as a Pi package and its extension loaded; generic RPC behavior lives in skills/drpc-rpc/
- Environments unwilling to install the Pi extension or pi-mcp-adapter, since the skill depends on Pi-provided tools like drpc_setup
- Situations needing instant MCP results — first-time setup may require a session reload or restart before the new MCP server appears
How do you install this skill?
- The skill auto-installs and configures an external MCP server (Coinbase Payments) and rewrites ~/.pi/agent/mcp.; review install contents and rollback options before use.
- The x402 flow may trigger an on-chain payment (up to 5 USDC on Base for new wallets); understand the cost path beforehand.
- Core function depends on drpc.org and overseas blockchain services, which may be unreachable from mainland-China networks.
- The Pi extension code and the sibling drpc-rpc skill are outside the reviewed evidence; their safety and quality are unverified.
- Publisher is not verified by FollowSkills and identity is unknown; this is a static source review with nothing executed.
- Shell / CLI
- Network access
- Local filesystem
- MCP Server
Pi Agent with the repository installed as a Pi packagepi-mcp-adapterCoinbase Payments MCP (payments-mcp)
The README documents Pi Agent installation as follows; the skill itself lives at .pi/skills/drpc-rpc-pi/SKILL.md and ships with the package, with Pi-specific setup documented separately in .pi/INSTALL.md:
Pi Agent
pi install npm:pi-mcp-adapter
pi install https://github.com/drpcorg/drpc-agent-skillsHow do you use this skill?
Once installed, send your agent any of these to trigger it:
- Set up DRPC MCP for me — I don't have an API key yet
- /drpc-setup
- /drpc-coinbase-wallet-setup
- Get the ETH balance of vitalik.eth on Ethereum
The skill is triggered two ways in Pi Agent: the agent calls its tools automatically, or the user runs slash commands manually.
Automatic flow (when DRPC MCP is missing):
- Check the MCP server list; if DRPC MCP is unavailable but drpc_setup exists, call it with no apiKey — the extension installs the Coinbase Payments MCP bundle and writes ~/.pi/agent/mcp..
- Re-check the list; if payments-mcp is still not visible, tell the user to reload or restart the Pi/MCP session.
- Once payments-mcp is visible, use it to acquire a DRPC API key via x402.
- Call drpc_setup again with the key to finish configuring DRPC MCP.
- If DRPC MCP is still unavailable in the current session, execute the request via the direct HTTP fallback in skills/drpc-rpc/direct-http.md.
Manual commands: /drpc-setup (DRPC API key setup) and /drpc-coinbase-wallet-setup (Coinbase Payments MCP setup).
What are this skill's strengths and limitations?
- Zero-config onboarding: the agent runs the full install, key acquisition, and config flow when no DRPC environment exists
- Wallet-equipped agents get keys via x402 + SIWE, free or instantly, with no signup
- Clear security boundary: never asks the user for private keys; wallet custody stays outside Pi
- Well-defined failure handling: prompts for a session restart when MCP is not picked up, with a direct HTTP fallback
- Pi Agent only — the overlay cannot be used on other platforms
- Long dependency chain: requires the Pi extension, pi-mcp-adapter, and Coinbase Payments MCP all working
- First setup may require reloading or restarting the Pi/MCP session before results appear in the same session
- No test suite or cross-platform validation is documented for this skill, and the README offers no separate maintenance notes for it
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 RPC — Pi Agent Setup Overlay this page | 50 · Use with care | ★ 23 | 4mo ago | MIT |
| DRPC Blockchain RPC Skill | 50 · Use with care | ★ 23 | 4mo ago | MIT |
| Code OSS Development Log Viewer ✓ Microsoft · Official | 51 · Use with care | ★ 194k | 10d ago | MIT |
| GitHub Copilot SDK Builder ✓ Microsoft · Official | 49 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Microsoft Foundry Agent Skill ✓ Microsoft · Official | 47 · Use with care | ★ 2.7k | 3mo ago | MIT |
How did FollowSkills review this skill?
The skill explicitly forbids asking for private keys in Pi, prefers Coinbase Agentic Wallet so custody stays outside Pi, discloses data flow (writes ~/.pi/agent/mcp.), and provides a direct HTTP fallback; however, the flow installs an external MCP (Coinbase Payments) and rewrites config automatically without documented confirmation or rollback, and the extension implementation is not present in evidence — deducted.
Steps are clear with failure branches (prompt reload if MCP invisible, fallback to direct HTTP when unavailable), giving basic failure feedback; but the drpc_setup and drpc_coinbase_wallet_setup implementations are outside the evidence, with no tests or edge cases, so key-path reproducibility cannot be verified statically — deducted.
Trigger conditions are fairly explicit (blockchain data, DRPC setup, x402 key acquisition, missing DRPC MCP) and non-fit is declared (Pi Agent only); but core function depends entirely on overseas services (drpc.org, x402/Base on-chain settlement), a material reachability risk from mainland China — deducted.
Docs are well layered (overlay separated from the generic skill), MIT license is clear, and package. gives install/dependency notes; but the skill hard-depends on extension and sibling files not shown in evidence, versioning is bare (0.1.0) with no changelog or maintenance statement — deducted.
The claimed value — automated DRPC MCP configuration and x402 key acquisition reducing manual setup — is plausible; but with zero execution evidence, output usability and actual outcomes (including possible 5 USDC payment) are unverified — deducted.
Auditable primary material exists (SKILL.md, README, package., LICENSE) making the flow traceable; but key claims (MCP tool behavior, x402 flow) lack tests or third-party execution corroboration, and coverage is thin — deducted.
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 →