fr.intrane/peage-mcp
Give your agent a prepaid fiat wallet: pay any API per call in cents, no crypto, spend caps.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
https://github.com/javimosch/peage-mcp/releases/download/v0.1.4/peage-mcp.mcpbEnvironment variables
PEAGE_URLRail instance to target (default https://peage.intrane.fr). Point at a self-hosted or staging rail.PEAGE_WALLET_TOKENsecret Existing wallet token (pw_...). If unset, peage_setup mints one and stores it at ~/.peage-mcp.json.
https://github.com/javimosch/peage-mcp/releases/download/v0.1.4/peage-mcp-darwin-universal.mcpbEnvironment variables
PEAGE_URLRail instance to target (default https://peage.intrane.fr). Point at a self-hosted or staging rail.PEAGE_WALLET_TOKENsecret Existing wallet token (pw_...). If unset, peage_setup mints one and stores it at ~/.peage-mcp.json.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
peage-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: javi@intrane.fr
Frequently asked questions
What is fr.intrane/peage-mcp?
Give your agent a prepaid fiat wallet: pay any API per call in cents, no crypto, spend caps.
How do I install fr.intrane/peage-mcp?
Follow the installation steps in its documentation, shown on this page and in its repository.
Does fr.intrane/peage-mcp need an API key?
Yes. It expects PEAGE_WALLET_TOKEN, which you set in its configuration.
Is fr.intrane/peage-mcp open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains fr.intrane/peage-mcp?
It is published by javimosch. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.