Invoice by Ouroboros Apps vs Billify
Invoice by Ouroboros Apps is an MCP server published by LAHutchins91. Marketplaces we read that list it: 1 (Official MCP Registry). Billify is an MCP server published by Ovindolo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |   Invoice by Ouroboros Apps | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.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 | Invoice by Ouroboros Apps | Billify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (invoice-continuity2.vercel.app/mcp) | Remote server (billify.org/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/lahutchins91/invoice-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | not checked yet |
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
Invoice by Ouroboros Apps
Freelance invoice line items, rates, due dates, and late terms for AI assistants
Billify
Invoicing for businesses and AI agents: invoices, crypto payments, compliance, Invoice Passports.
How to run each
Invoice by Ouroboros Apps As a remote MCP server
claude mcp add --transport http invoice https://invoice-continuity2.vercel.app/mcpBillify As a remote MCP server
claude mcp add --transport http billify https://billify.org/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 Invoice by Ouroboros Apps 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: Invoice by Ouroboros Apps · What it can do: Billify · Compare two other plugins
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.