Ext Ops Panel
Open dashboard
Comparison

Bitrefill vs comdirect

Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). comdirect is an MCP server published by mad4ms. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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

Where each is published
MarketplaceBitrefillcomdirect
Docker MCP Catalog Listed
Version: sha256:7ff5cc499284
Forks (GitHub): 1
Pulls (Docker Hub): 39 274
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 336
Forks (GitHub): 0
Stars (GitHub): 3
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 comdirect
FactBitrefillcomdirect
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)3 (better)
Pulls (Docker Hub) (differs)39 274No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/bitrefill)On your machine (comdirect-mcp)
Transportstdiostdio
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 18, secrets among them: 4
Licence (differs)MITNot stated
Repository (differs)github.com/bitrefill/bitrefill-mcp-servergithub.com/mad4ms/comdirect-mcp
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.

comdirect

In its own words, on Official MCP Registry:

Read-only access to comdirect accounts, transactions, depots, orders and postbox documents.

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)

comdirect As a local MCP server: PyPI package

Claude Code
claude mcp add --env "COMDIRECT_CLIENT_ID=<YOUR_COMDIRECT_CLIENT_ID>" --env "COMDIRECT_CLIENT_SECRET=<YOUR_COMDIRECT_CLIENT_SECRET>" --env "COMDIRECT_PASSWORD=<YOUR_COMDIRECT_PASSWORD>" --env "COMDIRECT_USERNAME=<YOUR_COMDIRECT_USERNAME>" --transport stdio comdirect-mcp -- uvx comdirect-mcp

Requires: COMDIRECT_CLIENT_ID (secret), COMDIRECT_CLIENT_SECRET (secret), COMDIRECT_PASSWORD (secret), COMDIRECT_USERNAME (secret)

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

Tools each declares

The marketplaces of comdirect 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 comdirect asks for

  • COMDIRECT_CLIENT_ID (secret)
  • COMDIRECT_CLIENT_SECRET (secret)
  • COMDIRECT_ENV_FILE
  • COMDIRECT_MCP_MASK_NAMES
  • COMDIRECT_MCP_PUSH_TAN_WAIT
  • COMDIRECT_MCP_UNMASK_IBANS
  • COMDIRECT_PASSWORD (secret)
  • COMDIRECT_USERNAME (secret)

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

What it can do: Bitrefill · What it can do: comdirect · 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.

Where the data comes from: how the catalog is built