Bitrefill vs PaidPilot Invoice Tools
Bitrefill is an MCP server published by bitrefill. Marketplaces we read that list it: 1 (Docker MCP Catalog). PaidPilot Invoice Tools is an MCP server published by api.paidpilot.io. 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 |  Bitrefill | |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 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
| Fact | Bitrefill | PaidPilot Invoice Tools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 39 358 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | On your machine (mcp/bitrefill) | Remote server (api.paidpilot.io/mcp) |
| 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 | Not stated |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 29 h 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
A Model Context Protocol Server connector for Bitrefill public API, to enable AI agents to search and shop on Bitrefill.
PaidPilot Invoice Tools
Invoice tools: reminders, late fees, terms, timesheets and a receivables health report (x402).
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/bitrefillRequires: BITREFILL_API_SECRET (secret)
PaidPilot Invoice Tools As a remote MCP server
claude mcp add --transport http invoice-tools https://api.paidpilot.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PaidPilot Invoice Tools has a remote endpoint we check. How we check endpoints
Tools each declares
Only Bitrefill has
categoriescreate_invoicedetailget_account_balanceget_invoiceget_invoicesget_orderget_orderspay_invoicepingsearchunseal_order
Only PaidPilot Invoice Tools has
invoice_from_timesheetlate_fee_calcpayment_reminder_draftpayment_terms_checkpricingreceivables_health_reportvalidate_invoice
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (PaidPilot Invoice Tools as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of PaidPilot Invoice Tools publish no settings it asks for, so we do not compare settings.
What it can do: Bitrefill · What it can do: PaidPilot Invoice Tools · 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.