Ext Ops Panel
Open dashboard
Comparison

Bitrefill vs Factur-X: Generate & Validate E-Invoices

Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). Factur-X: Generate & Validate E-Invoices is an MCP server published by LeBorgneAntoine. 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

Where each is published
MarketplaceBitrefillFactur-X: Generate & Validate E-Invoices
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.23
No figure published
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 Factur-X: Generate & Validate E-Invoices
FactBitrefillFactur-X: Generate & Validate E-Invoices
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Pulls (Docker Hub) (differs)39 360No figure on Docker Hub
Forks (GitHub) (differs)1No figure on GitHub
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/bitrefill)Remote server (facturx.orvel.dev/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-serverNot stated
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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.

Factur-X: Generate & Validate E-Invoices

In its own words, on Official MCP Registry:

Validate Factur-X, CII & UBL e-invoices free, no key. Generate compliant invoices from JSON.

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)

Factur-X: Generate & Validate E-Invoices As a remote MCP server

Claude Code
claude mcp add --transport http facturx https://facturx.orvel.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Factur-X: Generate & Validate E-Invoices has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Factur-X: Generate & Validate E-Invoices publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Factur-X: Generate & Validate E-Invoices publish no settings it asks for, so we do not compare settings.

What it can do: Bitrefill · What it can do: Factur-X: Generate & Validate E-Invoices · 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