Drain Mcp
Route agent inference spend through USDC micropayments on Polygon instead of hoarding provider API keys.
Overview
io.github.kimbo128/drain-mcp is a MCP server for the Build phase that pays for AI inference with USDC micropayments on Polygon via a funded wallet instead of vendor API keys.
What is this MCP server?
- USDC micropayments on Polygon for AI inference usage
- No traditional LLM vendor API keys required for the pay-per-use path
- stdio MCP package drain-mcp on npm at version 0.1.3
- Wallet funded via required secret DRAIN_PRIVATE_KEY environment variable
- Repository subfolder mcp under kimbo128/DRAIN on GitHub
- Package version 0.1.3 on npm identifier drain-mcp
- 1 required secret environment variable: DRAIN_PRIVATE_KEY
- Transport type stdio per server.schema.json
Community signal: 1 GitHub stars.
What problem does it solve?
Solo builders burning time on API key sprawl and opaque prepaid credits want per-inference billing they control on-chain.
Who is it for?
Indie agent builders experimenting with usage-based inference costs on Polygon who already manage a crypto wallet.
Skip if: Teams that need enterprise invoicing, fiat-only procurement, or zero crypto custody responsibility.
What do I get? / Deliverables
Your agent can call inference through MCP with micropayments from your Polygon USDC wallet after you register DRAIN_PRIVATE_KEY in the host.
- MCP-accessible inference billed via USDC micropayments
- Wallet-based payment path without vendor API keys on that route
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you wire payment rails into the agent stack alongside other integrations before you ship workloads that consume paid models. Integrations is the right subphase: wallet keys, stdio MCP transport, and inference billing are connection plumbing, not launch or growth tactics.
How it compares
On-chain micropayment MCP bridge, not a hosted LLM API marketplace skill.
Common Questions / FAQ
Who is drain-mcp for?
Developers wiring Claude Code or similar agents to Polygon USDC micropayments for inference instead of stacking traditional API keys.
When should I use drain-mcp?
During Build when you are integrating agent tooling and want pay-per-use inference economics on Polygon before you scale usage.
How do I add drain-mcp to my agent?
Add the npm stdio server drain-mcp to your MCP config and set the secret DRAIN_PRIVATE_KEY for your Polygon payment wallet.