io.github.theluckystrike/invoice
MCPB · INVOICE.MCPB · SCANNED SEP 21
Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Superseded by the word-rich registry name for this server at v0.21.0; the v0.1.1 bundle this row points at is three weeks and twenty releases old.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security22
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 157 of 158 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 157 of 158 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1006 tokens (~77/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · invoice.mcpb
Download bundleEvery change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Sept 26 47
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.1.1/invoice.mcpb@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| Deprecated | 2 |
| Stale | 63 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
business_set Set your business details ~218
Store the issuer profile printed at the top of every invoice: your name, address, VAT id, bank details and defaults (currency, tax rate, payment terms, invoice number prefix). Call this once before creating invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Postal address, newlines allowed |
| bank | string | – | Bank name / BIC |
| default_currency | string | – | ISO code, e.g. EUR, USD, JPY. Default EUR |
| default_tax_rate | number | – | Default VAT percent applied to items without their own rate |
| string | – | – | |
| iban | string | – | IBAN or account number for payment |
| invoice_prefix | string | – | Invoice number prefix, default INV (custom prefix is Pro) |
| logo_path | string | – | Path to a PNG or JPG logo (Pro) |
| name | string | yes | Your business or freelancer name |
| payment_terms_days | number | – | Default days until due. Default 14 |
| vat_id | string | – | VAT / tax registration id |
No output schema declared.
No examples provided.
client_add Add a client ~69
Store a client so invoices can refer to them by name. Re-adding the same name updates the stored details.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| string | – | – | |
| name | string | yes | – |
| vat_id | string | – | Client VAT id, printed for reverse-charge invoices |
No output schema declared.
No examples provided.
client_list List clients ~23
List every stored client with their id, address, email and VAT id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
invoice_create Create an invoice ~160
Create an invoice for a client from a list of items. Allocates the next invoice number (never reused), computes subtotal, discount, tax lines per rate and the total. Amounts are held as integer minor units; every line is rounded first, then summed.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client name or id. Unknown names are added automatically |
| currency | string | – | – |
| discount_percent | number | – | Discount percent applied to every line before tax, 0-100 |
| due_days | number | – | Days until due, defaults to your payment terms |
| issue_date | string | – | YYYY-MM-DD, defaults to today |
| items | array | yes | Line items |
| notes | string | – | Free text printed under the totals |
No output schema declared.
No examples provided.
invoice_from_hours Invoice from hours ~120
Shortcut for the common case: bill one client for N hours at an hourly rate. Creates a single-line invoice.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| currency | string | – | – |
| description | string | – | Line description, default 'Consulting services' |
| discount_percent | number | – | – |
| due_days | number | – | – |
| hours | number | yes | – |
| issue_date | string | – | – |
| notes | string | – | – |
| rate | number | yes | Hourly rate in major units |
| tax_rate | number | – | – |
No output schema declared.
No examples provided.
invoice_get Get one invoice ~32
Return the full stored record for one invoice number, including every line and tax breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | – |
No output schema declared.
No examples provided.
invoice_list List invoices ~67
List invoices, optionally filtered by status (unpaid, paid, partial), client, and an issue-date range.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | – |
| from | string | – | YYYY-MM-DD inclusive |
| status | string | – | – |
| to | string | – | YYYY-MM-DD inclusive |
No output schema declared.
No examples provided.
invoice_mark_paid Mark an invoice paid ~76
Record a payment. Without an amount the invoice is marked fully paid; a smaller amount marks it partial and reports the remaining balance.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount received in major units. Omit for the full total |
| number | string | yes | – |
| paid_date | string | – | YYYY-MM-DD, defaults to today |
No output schema declared.
No examples provided.
invoice_pdf Render invoice PDF ~94
Render an invoice as an A4 PDF you can send: issuer block, BILL TO client block, dates, item table with wrapped descriptions, subtotal, discount, tax lines per rate, total, payment details and notes. Every money value on the page carries its currency code. Returns the file path.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | – |
| out_path | string | – | Where to write the PDF. Defaults to the data directory |
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
overdue_report Overdue report ~62
Answer "which invoices are overdue?": every unpaid or partly paid invoice past its due date, with days overdue, the outstanding amount per invoice and the outstanding total per currency. Free and unlimited.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD, defaults to today |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/invoice MCP server?
io.github.theluckystrike/invoice is an MCP server listed in the public MCP registry as io.github.theluckystrike/invoice. Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.1.1/invoice.mcpb).
Is the io.github.theluckystrike/invoice MCP server safe to use?
io.github.theluckystrike/invoice scores 56 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.theluckystrike/invoice MCP server expose?
io.github.theluckystrike/invoice exposes 12 tools: business_set, client_add, client_list, invoice_create, invoice_from_hours, and 7 more. Their descriptions and schemas cost roughly 986 tokens of context every time the server is loaded.
Is the io.github.theluckystrike/invoice MCP server still maintained?
io.github.theluckystrike/invoice is marked deprecated in the MCP registry. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.theluckystrike/invoice MCP server under?
io.github.theluckystrike/invoice declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.