Peage MCP Server

Give your agent a prepaid fiat wallet: pay any API per call in cents, no crypto, spend caps. That is what the peage mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

One ~120 KB static binary, pure machin (MFL). No Node, no Python.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 7 tools. What each one is for:

• 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

What it needs from you

Configuration is passed through the environment: PEAGE_WALLET_TOKEN, PEAGE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Peage's toolset — peage_setup, peage_status, peage_topup and 4 more — is a fair guide to whether it matches your workflow. It is maintained by fr.intrane; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.