About peage-mcp
peage-mcp is a prepaid fiat wallet MCP server for agents that need to pay APIs per call. It combines wallet management, spending caps, paid requests, and receipt verification.
Key features
- 01Create a wallet and check balance
- 02Top up the wallet
- 03Make per-call paid API requests
- 04Set call and merchant limits
- 05Verify signed receipts
- 06Audit ledger solvency
Use cases
- 01Let an agent use pay-per-call APIs
- 02Set spending limits for API costs
MCP support
The MCP server exposes seven wallet and payment tools to MCP-capable agents.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEpeage-mcp — give your agent a wallet
An MCP server that puts a prepaid fiat wallet in any MCP-capable agent (Claude Code, Claude Desktop, anything speaking MCP stdio). The agent can then pay APIs per call on the peage rail — cents at a time, no crypto, no subscriptions, with spending caps you control.
One ~120 KB static binary, pure machin (MFL). No Node, no Python.
Install
Grab the binary (or ./build.sh with machin on PATH), then register it:
Claude Code (.mcp.json in your project, or ~/.claude.json for user scope):
{"mcpServers": {"peage": {"command": "/path/to/peage-mcp", "args": ["serve"]}}}
Claude Desktop (claude_desktop_config.json): same snippet under mcpServers.
What the agent gets (7 tools)
| tool | what it does |
|---|---|
peage_setup | mint the wallet once; token stored at ~/.peage-mcp.json |
peage_status | balance, escrow, caps, recent charges |
peage_topup | Stripe Checkout URL → the agent hands it to you, you pay once |
peage_paid_request | call any peage-metered API with the wallet attached |
peage_set_limits | per-call + per-merchant daily spending caps |
peage_verify_receipt | publicly verify any signed charge receipt |
peage_solvency | audit the rail's live ledger invariant |
The human appears exactly once in the loop: paying the top-up link. Everything else is the agent's business.
The 60-second demo
Ask your agent: "set up a peage wallet, then fetch https://peage.intrane.fr/demo/fortune
as a paid request" — it mints a wallet that comes with free starter credit, so it pays
the 1-cent toll and gets its fortune on the first try, no human needed. When the free
credit runs out, peage_topup hands you a Stripe link to fund more. That's the whole
agent-payment loop — and the agent completes it before you touch your card.
Security model
- The wallet token lives in
~/.peage-mcp.json(orPEAGE_WALLET_TOKEN). Sharing it with a merchant API is how they charge you — the caps bound the exposure: default 1€ per call / 10€ per merchant per day, adjustable viapeage_set_limits. - The rail stores only a hash of the token; every charge returns an HMAC-signed receipt
anyone can verify; the ledger invariant is public (
peage_solvency). PEAGE_URLpoints the server at a different rail instance (self-hosted, staging).
Sibling repos: peage (the rail, docs, skills) · x402: peage is a live x402 facilitator. An intrane.fr product. Contact: [email protected]
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.