Bitrefill vs MuPag Sandbox Payments
Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). MuPag Sandbox Payments is an MCP server published by mupag.com.br. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  Bitrefill |  MuPag Sandbox Payments |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7ff5cc499284 Forks (GitHub): 1 Pulls (Docker Hub): 39 343 Stars (Docker Hub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (npm): 123 Downloads/week (npm): 28 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 | Bitrefill | MuPag Sandbox Payments |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 39 343 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/bitrefill) | On your machine (@mupag/mcp-server) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bitrefill/bitrefill-mcp-server | Not stated |
| 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
Bitrefill
A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.
MuPag Sandbox Payments
Sandbox-only MuPag MCP server for approved payments, subscriptions, refunds, and reconciliation.
How to run each
Bitrefill As a local MCP server: Docker image
claude mcp add --env "BITREFILL_API_SECRET=<YOUR_BITREFILL_API_SECRET>" --transport stdio bitrefill -- docker run -i --rm -e BITREFILL_API_SECRET mcp/bitrefillRequires: BITREFILL_API_SECRET (secret)
MuPag Sandbox Payments As a local MCP server: npm package
claude mcp add --env "MUPAG_API_KEY=<YOUR_MUPAG_API_KEY>" --env "MUPAG_ENV=<YOUR_MUPAG_ENV>" --transport stdio mupag-sandbox-payments -- npx -y @mupag/mcp-serverRequires: MUPAG_API_KEY (secret), MUPAG_ENV
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of MuPag Sandbox Payments publish no list of tools, so we do not compare tools.
Settings each asks for
Only Bitrefill asks for
BITREFILL_API_IDBITREFILL_API_SECRET (secret)
Only MuPag Sandbox Payments asks for
MUPAG_API_KEY (secret)MUPAG_ENV
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Bitrefill · What it can do: MuPag Sandbox Payments · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.