
Drain Mcp
io.github.kimbo128Published by GitHub account kimbo128v0.1.3Updated Oct 24, 2026
Pay for AI inference with USDC micropayments on Polygon. No API keys needed.
Overview
A local MCP server that lets an assistant discover AI marketplace providers and pay for their services with USDC micropayments on Polygon, without API keys.
- What you can do
- Discover providers and read their usage docs, filtered by model, category or online status, including LLM, image, audio, code, scraping and VPN services. Check wallet USDC and gas balance and approve USDC spending for the payment contract. Open, list and inspect payment channels, including deposits, spending and expiry. Send paid requests through a channel to any provider type, or pay per request to MPP providers for chat and REST calls. Close channels cooperatively for an instant refund or reclaim funds after expiry, and report provider success or failure.
- When to use it
- Useful when an assistant needs to call external services such as LLM inference, search, scraping or image generation without holding API keys, and when paying per request in USDC is acceptable. Not needed if you already have API keys for the services you want or the task requires no external services.
- Requirements
- Runs as a local npm package (drain-mcp) over stdio, desktop only. Requires a Polygon wallet private key in the DRAIN_PRIVATE_KEY environment variable and USDC on Polygon Mainnet; optional variables set the chain ID, RPC URL and MPP maximum deposit. Network access to handshake58.com, provider endpoints and a Polygon RPC is needed.
Installation
In SourceWeft
- Open Drain Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
DRAIN MCP Server
Payments for AI Agents — No API keys, no credit cards, no subscriptions.
MCP server for the Handshake58 AI Marketplace. Agents discover service providers, pay automatically, and call any service — LLM inference, web scraping, image generation, search, and more.
Supports two payment protocols:
- DRAIN — Payment channels on Polygon. Open once, send many requests, close when done.
- MPP — Per-request payments via Tempo. Each request is paid individually. No channel needed.
When to Use
Use drain-mcp when you need to:
- Call any service (LLM, search, scraping, image gen, etc.) without API keys
- Pay per-request with USDC — no subscriptions, no credit cards
- Access 30+ providers through one unified interface
Do NOT use drain-mcp when:
- You already have API keys for the service you need
- The task doesn't require external services
TL;DR - Minimum Viable Workflow
MPP Providers (per-request, no channel)
DRAIN Providers (payment channels)
When to Close a Channel
-
Done with your task? → Use
drain_cooperative_close(channelId). Instant refund of unspent deposit. Always do this when finished. -
Planning more requests soon? → Keep the channel open. No need to close and reopen — saves $0.04 in gas fees.
-
Channel expired? → Use
drain_close_channel(channelId). Reclaims unspent USDC after the expiry timestamp. Funds do NOT return automatically.
Rule of thumb: Close when the task is done. Keep open while working.
Already Hit a 402?
MPP providers: drain-mcp handles 402 automatically via mppx/Tempo. Just use mpp_chat or mpp_request — payment is resolved transparently.
DRAIN providers return 402 Payment Required with headers when no payment voucher is sent:
DRAIN Flow:
- Call a provider endpoint (no voucher) → get
402with headers - Install
drain-mcpor use the signing API at theX-Payment-SigningURL - Open a channel to the
X-Payment-Provideraddress - Retry the request with an
X-DRAIN-Voucherheader
Everything you need is in the 402 response. No prior registration required.
Tools Reference
Discovery
drain_providers
Find service providers. Filter by model name, category, or online status.
Categories: llm, image, audio, code, scraping, vpn, multi-modal, other
drain_provider_info
Get details about a provider including usage instructions (docs). The docs explain how to format requests for that provider.
Wallet
drain_balance
Check wallet USDC balance, POL for gas, and DRAIN contract allowance.
drain_approve
Approve USDC spending for the DRAIN contract. Required once before opening channels.
Channels
drain_open_channel
Open a payment channel. Locks USDC for the specified duration.
Returns channelId, expiry time, and provider usage docs.
drain_channel_status
Check a channel's deposit, spending, remaining balance, and expiry.
drain_channels
List all known channels with status (active/expired/closed). Find expired channels that need closing.
Usage (DRAIN)
drain_chat
Send a paid request through a DRAIN channel. Works for ALL DRAIN provider types:
- LLM providers: Standard chat messages
- Non-LLM providers: JSON payload in the user message content (check provider docs)
Usage (MPP)
mpp_chat
Send a chat request to an MPP LLM provider. Payment is automatic via Tempo — no channel, no setup.
mpp_request
Send a request to an MPP REST API service (Tavily, Brave, Wolfram, etc.). Payment is automatic via Tempo.
Read the provider's docs first (drain_provider_info) to find the correct endpoint paths and request format.
Quality Feedback
drain_feedback
Report success or failure after using any provider (DRAIN or MPP). Feeds the marketplace quality scoring system.
Settlement
drain_cooperative_close
Close a channel early with provider consent. Use this when your task is done — instant refund of unspent deposit. No need to wait for expiry.
drain_close_channel
Close an expired channel and reclaim unspent USDC. Use when the channel has passed its expiry timestamp.
Economics Example
Opening a GPT-4o channel:
- Protocol fee: 2% on provider claims (on-chain)
- Session fee: none
- Live pricing:
GET https://handshake58.com/api/mcp/providers
Provider Categories
Providers are not limited to LLM chat. Each provider has a category field and a docs endpoint explaining how to format requests.
Rule: For any category other than llm, call drain_provider_info first to read the docs.
Decision Trees
Choosing a Protocol
Starting a DRAIN Session
Ending a DRAIN Session
Choosing Amount and Duration
Handling Errors
Setup
1. Install
2. Create a Wallet (locally)
Generate a key on your own machine — nothing is sent over the network:
3. Fund the Wallet
Send $1–5 USDC on Polygon Mainnet to your wallet address. Use a dedicated low-value wallet — never your main wallet.
No POL needed — if your wallet holds $5+ USDC, free gas is provided:
Returns 0.1 POL (~10K transactions). Sends only your public address.
4. Configure MCP Client
Environment Variables
Security & Privacy
Key Handling
DRAIN_PRIVATE_KEY is loaded into memory by the local MCP process. It is used for:
- EIP-712 voucher signing for DRAIN channels (off-chain, no network call)
- On-chain transaction signing (signed locally, only the signature is broadcast)
- Tempo payment signing for MPP requests (handled by mppx, signed locally)
The key is never transmitted to any server. Providers verify signatures against on-chain state.
Spending Limits
DRAIN: Exposure is capped by the smart contract:
- Maximum spend = channel deposit (you choose the amount)
- Channel has a fixed duration (you choose)
- After expiry, unspent funds are reclaimable via
drain_close_channel
MPP: Each request is paid individually at the provider's advertised price. No pre-deposit required.
Both protocols: No recurring charges, no stored payment methods.
What Leaves Your Machine
- Public API queries to handshake58.com (provider list, config, channel status)
- Request messages to providers (sent to the provider's apiUrl, NOT to Handshake58)
- Signed payment vouchers (contain a cryptographic signature, not the key)
- Signed on-chain transactions (broadcast to Polygon RPC)
What Stays Local
- Private key (never transmitted)
- All cryptographic operations (signing happens in-process)
External Endpoints
Every network request the MCP server makes:
Safeguards
- Use a dedicated wallet with $1–5 USDC. Never reuse your main wallet.
- Always generate keys locally. The key stays on your machine.
- Open source: github.com/kimbo128/DRAIN (MIT licensed)
- Open channels with small deposits. Close promptly when done.
Links
- NPM: https://www.npmjs.com/package/drain-mcp
- GitHub: https://github.com/kimbo128/DRAIN
- Marketplace: https://handshake58.com
- Provider Directory: https://handshake58.com/directory
- Contract:
0x0C2B3aA1e80629D572b1f200e6DF3586B3946A8A(Polygon Mainnet)
Source: mcp/README.md at commit 50b3a11
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts