fr.intrane/peage-mcp vs io.github.codespar/mcp-wise
fr.intrane/peage-mcp is an MCP server published by intrane.fr. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.codespar/mcp-wise is an MCP server published by codespar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  fr.intrane/peage-mcp |  io.github.codespar/mcp-wise |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.5 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (npm): 163 Downloads/week (npm): 47 Forks (GitHub): 52 Stars (GitHub): 279 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | fr.intrane/peage-mcp | io.github.codespar/mcp-wise |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 279 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 52 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (https://github.com/javimosch/peage-mcp/releases/download/v0.1.4/peage-mcp.mcpb) | On your machine (@codespar/mcp-wise) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/javimosch/peage-mcp | github.com/codespar/mcp-dev-latam |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
fr.intrane/peage-mcp
Give your agent a prepaid fiat wallet: pay any API per call in cents, no crypto, spend caps.
io.github.codespar/mcp-wise
MCP server for Wise — multi-currency accounts, FX, international transfers, quotes, recipients
How to run each
fr.intrane/peage-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: PEAGE_WALLET_TOKEN (secret)
io.github.codespar/mcp-wise As a local MCP server: npm package
claude mcp add --env "WISE_API_TOKEN=<YOUR_WISE_API_TOKEN>" --transport stdio mcp-wise -- npx -y @codespar/mcp-wiseRequires: WISE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only fr.intrane/peage-mcp asks for
PEAGE_URLPEAGE_WALLET_TOKEN (secret)
Only io.github.codespar/mcp-wise asks for
WISE_API_TOKEN (secret)WISE_ENV
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: fr.intrane/peage-mcp · What it can do: io.github.codespar/mcp-wise · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.