Peage Mcp

fr.intranePublished by intrane.frv0.1.5Updated Oct 24, 2026

Give your agent a prepaid fiat wallet: pay any API per call in cents, no crypto, spend caps.

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an AI assistant a prepaid fiat wallet so it can pay metered APIs per call in cents, with spending caps.

What you can do
Set up a wallet and check its balance, escrow, caps and recent charges, with a token stored locally or supplied by environment variable. Top up by generating a Stripe Checkout link for the user to pay once. Make paid requests to any peage-metered API with the wallet attached. Set per-call and per-merchant daily spending caps. Verify signed charge receipts and audit the rail's public ledger invariant.
When to use it
Use it when an assistant should call pay-per-use APIs on the peage rail and settle each call in fiat cents without subscriptions or crypto, while the user keeps control through spending caps and a single top-up payment.
Requirements
Runs as a local process on the desktop from a static binary; no Node or Python needed. PEAGE_URL optionally selects the rail instance (defaults to the hosted one). PEAGE_WALLET_TOKEN optionally supplies an existing wallet token; otherwise setup mints one and stores it at ~/.peage-mcp.json. Network access to the rail and to Stripe for top-ups.
Before you install
The wallet token is a spending credential: it is shared with merchant APIs so they can charge, and anyone holding it may be able to spend within the caps. Default caps are 1 euro per call and 10 euros per merchant per day; review them before use. Top-ups involve real payment through a Stripe link the user must complete. The server writes a token file to the home directory and sends charge data to the rail.

Installation

In SourceWeft

  1. Open Peage Mcp in the dashboard and add it to a workspace.
  2. 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

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):

json
{"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)

toolwhat it does
peage_setupmint the wallet once; token stored at ~/.peage-mcp.json
peage_statusbalance, escrow, caps, recent charges
peage_topupStripe Checkout URL → the agent hands it to you, you pay once
peage_paid_requestcall any peage-metered API with the wallet attached
peage_set_limitsper-call + per-merchant daily spending caps
peage_verify_receiptpublicly verify any signed charge receipt
peage_solvencyaudit 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 (or PEAGE_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 via peage_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_URL points 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]

Source: README.md at commit 1816182

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

40% 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

    Declare a license in the repository or the registry entry.