billing-plane vs io.github.eliaskress/flowcheck
billing-plane is a plugin bundle for AI coding tools published by kamesh231. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.eliaskress/flowcheck is an MCP server published by eliaskress. 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
| Marketplace |  billing-plane |  io.github.eliaskress/flowcheck |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.3 Downloads/month (npm): 146 Downloads/week (npm): 25 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-plane | io.github.eliaskress/flowcheck |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@flowcheck/mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kamesh231/billingplane | github.com/eliaskress/flowcheck-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
billing-plane
BillingPlane is a Stripe billing intelligence plugin for Claude that prevents common revenue-losing billing bugs during development. Instead of adding another billing middleware or SDK into your production stack, BillingPlane works at build time. It teaches Claude how to generate correct billing logic, webhook handlers, entitlements, and usage billing patterns directly in your codebase. BillingPlane encodes 4,000+ lines of production billing patterns including lifecycle handling, idempotent Stripe webhook processing, subscription state management, credit systems, and feature gating. When developers run BillingPlane commands, Claude generates production-ready billing code that follows strict guardrails used in real SaaS systems. The result is a vendor-free billing architecture: developers keep full control of their code while avoiding common Stripe mistakes such as duplicate webhooks, incorrect subscription states, entitlement drift, or broken usage billing. BillingPlane includes commands for auditing existing
io.github.eliaskress/flowcheck
Stripe payouts, Shopify orders, and bank transactions unified for reconciliation and cash flow
How to run each
billing-plane As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install billing-plane@claude-communityio.github.eliaskress/flowcheck As a local MCP server: npm package
claude mcp add --env "FLOWCHECK_API_KEY=<YOUR_FLOWCHECK_API_KEY>" --transport stdio flowcheck -- npx -y @flowcheck/mcp-serverRequires: FLOWCHECK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of billing-plane publish no settings it asks for, so we do not compare settings.
What it can do: billing-plane · What it can do: io.github.eliaskress/flowcheck · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.