Ext Ops Panel
Open dashboard
Comparison

Bitrefill vs mnemopay

Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). mnemopay is a plugin bundle for AI coding tools published by mnemopay. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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

Where each is published
MarketplaceBitrefillmnemopay
Docker MCP Catalog Listed
Version: sha256:7ff5cc499284
Forks (GitHub): 1
Pulls (Docker Hub): 39 358
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.2.0
Forks (GitHub): 4
Stars (GitHub): 8
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

Bitrefill vs mnemopay
FactBitrefillmnemopay
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)8 (better)
Pulls (Docker Hub) (differs)39 358No figure on Docker Hub
Forks (GitHub) (differs)1 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/bitrefill)On your machine (@mnemopay/sdk)
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle9
Licence (differs)MITApache-2.0
Repository (differs)github.com/bitrefill/bitrefill-mcp-servergithub.com/mnemopay/mnemopay-sdk
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Docker MCP Catalog:

A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.

mnemopay

In its own words, on Claude Code: claude-plugins-community:

Payment infrastructure for AI agents. Agent Credit Score (300-850), real payment rails (Stripe/Paystack/Lightning), autonomous shopping with escrow, hash-chained ledger, and behavioral finance. Charge for tool usage, track spending, shop autonomously, and build agent creditworthiness all from Claude Code.

How to run each

Bitrefill As a local MCP server: Docker image

Claude Code
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)

mnemopay As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mnemopay@claude-community

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of mnemopay publish no list of tools, so we do not compare tools.

Settings each asks for

Only Bitrefill asks for

  • BITREFILL_API_ID
  • BITREFILL_API_SECRET (secret)

Only mnemopay asks for

  • MNEMOPAY_PERSIST_DIR

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Bitrefill · What it can do: mnemopay · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built