Peage MCP server
What it does
Peage-mcp is an MCP server that gives an agent a prepaid fiat wallet to pay for API calls on a per-use basis through the peage rail. It eliminates the need for API subscriptions by letting agents charge cents per call, with spending caps controlled by the user.
- An agent calls a metered API and automatically pays the usage fee from its wallet without asking permission each time.
- You set spending limits per call and per merchant, then let your agent operate autonomously within those bounds.
- You fund the wallet once via Stripe when free starter credit runs out, and the agent continues making paid API calls.
Tools this server exposes
| Tool | Does |
|---|---|
| peage_setup | Initialize the wallet once; stores the token locally at ~/.peage-mcp.json |
| peage_status | Check wallet balance, escrow, spending caps, and recent charges |
| peage_topup | Generate a Stripe Checkout URL to fund the wallet with fiat |
| peage_paid_request | Make an HTTP request to any peage-metered API with the wallet attached for payment |
| peage_set_limits | Set per-call and per-merchant daily spending caps |
| peage_verify_receipt | Publicly verify an HMAC-signed charge receipt from the rail |
| peage_solvency | Audit the peage rail's live ledger invariant for transparency |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.