io.github.theluckystrike/expenses
io.github.theluckystrike/expenses
Is the io.github.theluckystrike/expenses MCP server down? Yes. It has given no valid answer since 2026-10-31: install failed.
Log expenses, receipts and mileage from chat: categorise, split VAT, summarise, export.
install failed down since 2026-10-31 · probed 2026-11-15 · unchanged since 2026-11-07
the bundle does not match the SHA-256 in the registry entry
- Bundle
- https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/expense-tracker.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/theluckystrike/mcp-servers
- Website
- https://mcp.zovo.one/s/expense-tracker
- Registry
- active, updated 2026-10-14 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- io.github.theluckystrike/duplicate-invoice-check · alive
- io.github.theluckystrike/estimates · install failed
- io.github.theluckystrike/exchange-fx · install failed
- io.github.theluckystrike/expense-tracker · alive
- io.github.theluckystrike/fixed-assets · install failed
- io.github.theluckystrike/freelance · install failed
- io.github.theluckystrike/glossary-terms-definitions-library · install failed
- io.github.theluckystrike/hourly-rate · alive
Servers that mention expenses.
- Doklad.ai ai.doklad/mcp · needs auth
- Dynt ai.dynt.api/dynt · needs auth
- ai.smithery/HARJAP-SINGH-3105-splitwise_mcp · not found
- Ledgy app.ledgy/ledgy · needs auth
- Manilo app.manilo/manilo · needs auth
- Mini Accountant app.miniaccountant/mini-accountant · needs auth
- ai.smithery/mrugankpednekar-bill_splitter_mcp · not found
- WalleK app.wallek/wallek · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-31, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.