billing-best-practices vs InvoiceBloom
billing-best-practices is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
billing-best-practices is a plugin bundle for AI coding tools published by Commet. No marketplace we read lists it any more. InvoiceBloom is an MCP server published by theasteve. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  InvoiceBloom | |
|---|---|---|
| Community marketplace commet-labs/billing-best-practices | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 2 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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
| Fact | billing-best-practicesno longer listed · | InvoiceBloom |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) (differs) | 2 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (invoicebloom.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/commet-labs/billing-best-practices | github.com/theasteve/invoicebloom-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of billing-best-practices
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Real-time billing infrastructure for AI products: create products, track usage, manage wallets, and verify pricing directly from Claude.
-
VP Revenue Ops: customer invoicing, recurring billing, and commission payout.
-
Manage companies, plans, features, and billing through SchematicHQ
-
stripe-billing io.github.theluckystrike/stripe-billing
Read your Stripe billing data from AI chat: balances, invoices, subscriptions. Read-only.
-
Interact with Stripe services over the Stripe API.
-
Set up and integrate Credyt — real-time monetization infrastructure for AI products.
What each says it does
billing-best-practices
SaaS billing best practices. Patterns for subscription lifecycle, failed payments, proration, multi-currency, tax compliance, plan changes, invoicing, and launch checklists.
InvoiceBloom
Create, send and track invoices for freelancers and small businesses.
How to run each
billing-best-practices
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
InvoiceBloom As a remote MCP server
claude mcp add --transport http invoicebloom https://invoicebloom.io/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 InvoiceBloom has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: billing-best-practices · What it can do: InvoiceBloom · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.