ledger vs Spliteo
ledger is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
ledger is a plugin bundle for AI coding tools published by eternal-roman / Ledger maintainers. No marketplace we read lists it any more. Spliteo is an MCP server published by spliteo.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  Spliteo | |
|---|---|---|
| Community marketplace eternal-roman/ledger | Removed on 2026-10-15 Version: 0.19.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.30.12 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 | ledgerno longer listed · | Spliteo |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.spliteo.app/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) | 11 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/eternal-roman/ledger | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 25 h ago, requires a key |
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 ledger
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Personal finance skills and MCP server for Ledgr
-
cashflow io.github.adam-messinger/cashflow
Personal finance ledger for AI agents — query spending, track bills, forecast cash flow.
-
Plain-text accounting for Claude Code: a git-backed Beancount cloud book, AI ingestion of statements/receipts, and HTML/Excel reports.
-
Household finance memory, budgets, transactions, and monthly reviews for AI assistants.
-
BankMCP™ for Claude Code: /bank:setup walks you through installing it locally, /bank:deploy through hosting it; plus a skill with account mapping, categorisation rules and a…
-
Log, query, and edit expenses, budgets, and accounts in Ledgy from any MCP-compatible AI assistant.
What each says it does
ledger
Deterministic financial-correctness guardrails: Money.from always, validated JournalEntry + Ledger.apply, audit-hashed ledgers, citations, no floats, provable balance + invariants.
Spliteo
Split group expenses, settle debts and track budgets in 107 currencies. Needs Spliteo Premium.
How to run each
ledger
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Spliteo As a remote MCP server
claude mcp add --transport http spliteo https://api.spliteo.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Spliteo 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: ledger · What it can do: Spliteo · 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.