Ext Ops Panel
Open dashboard
Comparison

Bitrefill vs Invoice & Payment ID Validator

Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). Invoice & Payment ID Validator is an MCP server published by invoice-validator.mohamed-bahaa53000.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
MarketplaceBitrefillInvoice & Payment ID Validator
Docker MCP Catalog Listed
Version: sha256:7ff5cc499284
Forks (GitHub): 1
Pulls (Docker Hub): 39 706
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.1
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

Bitrefill vs Invoice & Payment ID Validator
FactBitrefillInvoice & Payment ID Validator
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Pulls (Docker Hub) (differs)39 706No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)On your machine (mcp/bitrefill)Remote server (invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/bitrefill/bitrefill-mcp-servergithub.com/mowaah/invoice-validator-mcp
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-18
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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.

Invoice & Payment ID Validator

In its own words, on Official MCP Registry:

Pay/review/hold verdict for invoice payees: cross-checks IBAN, BIC, VAT, EIN. Paid: RapidAPI

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)

Invoice & Payment ID Validator As a remote MCP server

Claude Code
claude mcp add --transport http invoice-payment-id-validator https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp

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

Only Invoice & Payment ID Validator has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Invoice & Payment ID Validator publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Invoice & Payment ID Validator publish no settings it asks for, so we do not compare settings.

What it can do: Bitrefill · What it can do: Invoice & Payment ID Validator · 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