Bitrefill vs Porto Bank MCP
Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). Porto Bank MCP is an MCP server published by mcp-dir. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7ff5cc499284 Forks (GitHub): 1 Pulls (Docker Hub): 39 360 Stars (Docker Hub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Porto Bank MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 39 360 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/bitrefill) | Remote server (api.mcp.ai/p_portobank) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bitrefill/bitrefill-mcp-server | github.com/mcp-dir/portobank-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-14 |
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.
Porto Bank MCP
Connect your Porto Bank account to AI via Brazil's Open Finance: balances, statements, cards, invest
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/bitrefill
Requires: BITREFILL_API_SECRET (secret)
Porto Bank MCP As a remote MCP server
claude mcp add --transport http portobank-mcp https://api.mcp.ai/p_portobank
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Porto Bank MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Porto Bank MCP publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Porto Bank MCP publish no settings it asks for, so we do not compare settings.
What it can do: Bitrefill · What it can do: Porto Bank MCP · 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.