io.github.theluckystrike/invoice-maker
mcp-invoice
Make PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.
alive probed 2026-10-15 · HTTP 200
13tools
4.9ktokens in Claude Opus 5.5
5.0ktokens in Claude Code
2.4 %of a 200k context window
2.8ko200k_base estimate
91 msto initialize
73 msto list tools
- Endpoint
- https://mcp.zovo.one/mcp/invoice-maker (streamable-http)
- Host
- mcp.zovo.one
- Protocol
- 2025-11-25
- Reports itself as
- mcp-invoice 0.22.6
- Capabilities
- prompts, resources, tools
- Instructions
- none
- Claude count
- Claude Opus 5.5, measured 2026-10-05. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/theluckystrike/mcp-servers
- Website
- https://mcp.zovo.one/s/invoice
- Registry
- active, updated 2026-09-23 · registry entry
- Reachable
- 6 of the last 6 probes
Most expensive tools
| Tool | Tokens (o200k) | Share of this server |
|---|---|---|
| invoice_create | 622 | 22 % |
| invoice_from_hours | 556 | 20 % |
| business_set | 447 | 16 % |
| invoice_mark_paid | 207 | 7 % |
| invoice_pdf | 204 | 7 % |
Same tool set as 4 other servers
These registry entries have the same tool names and the same schema sizes.
- io.github.theluckystrike/freelance-invoice mcp.zovo.one
- io.github.theluckystrike/invoice-generator mcp.zovo.one
- io.github.theluckystrike/invoice-generator-freelancers mcp.zovo.one
- io.github.theluckystrike/invoice-pdf-billing-generator mcp.zovo.one
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-05 16:34 | alive | 91 ms | 13 | 4.9k | 2.8k |
| 2026-10-05 00:56 | alive | 57 ms | 13 | 2.8k | |
| 2026-10-04 10:07 | alive | 52 ms | 13 | 2.8k | |
| 2026-10-04 08:01 | alive | 35 ms | 13 | 2.8k | |
| 2026-10-03 20:40 | alive | 81 ms | 13 | 2.8k | |
| 2026-10-03 17:55 | alive | 88 ms | 13 | 2.8k |
Badge and feed
[](https://mcpcost.ulehla.dev/s/io.github.theluckystrike/invoice-maker)
An entry for every probe that changed the result, the tool count or the token cost: Atom feed. Add it to a feed reader or a Slack RSS app to hear when the server stops answering or its tool set grows.