# io.github.theluckystrike/invoice-pdf-billing-generator (remote · mcp.zovo.one)

Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 82/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/mcp-invoice.md), [page](https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/mcp-invoice)
- mcpb · `invoice.mcpb`: 46/100, [markdown](https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-invoice-mc.md), [page](https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-invoice-mc)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/invoice`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1924 tokens (~128/item across 15 items; 13 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "client_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.theluckystrike/invoice-pdf-billing-generator MCP server?

io.github.theluckystrike/invoice-pdf-billing-generator is a hosted endpoint at https://mcp.zovo.one/mcp/invoice, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http theluckystrike-invoice-pdf-billing-generator 'https://mcp.zovo.one/mcp/invoice'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-invoice-pdf-billing-generator": {
      "url": "https://mcp.zovo.one/mcp/invoice"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-invoice-pdf-billing-generator": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/invoice"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-invoice-pdf-billing-generator]
url = "https://mcp.zovo.one/mcp/invoice"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-invoice-pdf-billing-generator": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/invoice",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-invoice-pdf-billing-generator --url 'https://mcp.zovo.one/mcp/invoice' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-invoice-pdf-billing-generator:
    url: "https://mcp.zovo.one/mcp/invoice"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-invoice-pdf-billing-generator": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/invoice"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-invoice-pdf-billing-generator -t streamable-http -u 'https://mcp.zovo.one/mcp/invoice'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-invoice-pdf-billing-generator": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/invoice"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 82, +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.

### 2026-09-18 (score 81, +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.

### 2026-09-17 (score 80, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 77, +1)

- [security] Tool “client_add” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] Schema quality: good → excellent
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 76, 0)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “overdue_report” rewrote its description, which is the text the model reads
- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “invoice_pdf” rewrote its description, which is the text the model reads
- [security] Tool “invoice_mark_paid” rewrote its description, which is the text the model reads
- [security] Tool “invoice_list” rewrote its description, which is the text the model reads
- [security] Tool “invoice_create” rewrote its description, which is the text the model reads
- [security] Tool “client_list” rewrote its description, which is the text the model reads
- [security] Tool “client_delete” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

## MCP tools (13)

### `business_set` (~352 tokens)

Set your business details

The ONE business profile for the whole suite: name, address, VAT id, bank details and defaults (currency, tax rate, terms, prefix, timezone). Saved to the shared profile every other server reads. Call it once, first.

Input parameters:

- `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
- `email` (string): Your own email address. Leave it out unless the user gave it: no server ever fills an email from anything but this profile or an explicit argument
- `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, required): Your business or freelancer name
- `payment_terms_days` (number): Default days until due. Default 14
- `phone` (string): Your own phone number. Same rule as email: only if the user gave it
- `tax_rate` (number): Alias for default_tax_rate
- `timezone` (string): IANA zone you work in, e.g. Europe/Warsaw. Shared with time-tracker (entries are stamped in it) and timezone (your home zone)
- `vat` (number): Alias for default_tax_rate
- `vat_id` (string): VAT / tax registration id
- `vat_rate` (number): Alias for default_tax_rate

### `client_add` (~93 tokens)

Add a client

Store a client so invoice_create can refer to them by name. Re-adding the same name updates the stored address, email and VAT id; a record identical to a stored one is refused, naming the id that already holds it.

Input parameters:

- `address` (string)
- `email` (string)
- `name` (string, required)
- `vat_id` (string): Client VAT id, printed for reverse-charge invoices

### `client_delete` (~62 tokens)

Delete a client

Delete one stored client that nothing refers to. A client named on any invoice, quote, credit note, purchase order, deposit, statement or schedule is refused with those documents listed.

Input parameters:

- `client` (string, required): Client name or id, exactly as client_list shows it

### `client_list` (~49 tokens)

List clients

List every stored client with id, address, email and VAT id. No arguments, and it writes nothing. With none stored it says so: invoice_create also creates a client from the name you pass.

### `invoice_create` (~243 tokens)

Create an invoice

Create an invoice from line items and return the record with its next, never-reused number. unit_price is in MAJOR units; lines are rounded then summed. One currency per invoice. Free: 3 a month.

Input parameters:

- `client` (string, required): Client name or id. Unknown names are added automatically
- `currency` (string): Invoice currency, 3-letter ISO code. Defaults to the one currency every item agrees on, else your business default. Every line on one invoice must agree with it; a mix is refused with the exact conve…
- `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, required): Line items. Amounts are held as integer minor units and every line is rounded first, then summed, so the printed lines can never disagree with the total. A line may carry its own currency
- `notes` (string): Free text printed under the totals

### `invoice_from_hours` (~405 tokens)

Invoice from hours

Shortcut for the common case: bill one client for N hours at an hourly rate. Creates and returns a single-line invoice, converting the rate into target_currency when you supply fx_rates, and echoing back any entry_ids.

Input parameters:

- `client` (string, required)
- `currency` (string): Currency the rate is in. Without target_currency this is also the invoice currency
- `description` (string): Line description, default 'Consulting services'
- `discount_percent` (number)
- `due_days` (number)
- `entry_ids` (array): Time-tracker entry ids these hours came from (the entry_ids invoice_summary returns). Echoed back with the new invoice number so you can call entry_mark_billed
- `fx_rates` (object): Conversion rates, the same pair expense_to_invoice takes: fx_rates maps the RATE's currency to the number of target units one of it buys, meaning 1 unit of that currency = X units of target_currency,…
- `hours` (number, required)
- `issue_date` (string)
- `notes` (string)
- `rate` (number, required): Hourly rate in major units, expressed in currency (or the business default currency)
- `round_total` (boolean): D-R46: when converting with fx_rates, round the line's TOTAL to the exact converted amount instead of rounding the hourly rate to cents first. Default false keeps the D-R24 basis (unit price x hours…
- `target_currency` (string): Issue the invoice in this currency instead, converting the rate. Needs fx_rates for the rate currency
- `tax_rate` (number)

### `invoice_list` (~88 tokens)

List invoices

List invoices by number: client, dates, currency, subtotal, discount, tax lines, total, status, paid, credited and the balance still due after any credit note. Filter by status, client and date range.

Input parameters:

- `client` (string)
- `from` (string): YYYY-MM-DD inclusive
- `status` (string)
- `to` (string): YYYY-MM-DD inclusive

### `invoice_get` (~49 tokens)

Get one invoice

Return the full stored record for one invoice number, including every line, tax breakdown, and the balance still open after any credit note issued against it (see credited_minor).

Input parameters:

- `number` (string, required)

### `invoice_mark_paid` (~156 tokens)

Mark an invoice paid

Record a payment on one invoice. amount is in MAJOR units and ADDS to what is paid, never replaces it; omit it to settle the rest. An overpayment is refused, naming the open balance.

Input parameters:

- `amount` (number): Amount received in major units, ADDED to what is already paid on this invoice. Omit to pay off the remaining balance in full
- `method` (string): How it was paid, e.g. bank transfer, card. Stored on this payment's row
- `number` (string, required)
- `paid_date` (string): YYYY-MM-DD, defaults to today
- `reference` (string): Bank reference or transaction id for this payment. Stored on this payment's row

### `invoice_pdf` (~164 tokens)

Render invoice PDF

Call this tool to write one stored invoice as an A4 PDF and return the path: issuer, BILL TO, dates, items, taxes and totals. Free stamps a credit line and no logo; Pro renders it unbranded with your logo.

Input parameters:

- `number` (string, required): Invoice number to render, as returned by invoice_create
- `out_path` (string): Where to write the PDF; defaults to <data dir>/pdf/<number>.pdf. The page carries the issuer block, the BILL TO client block, dates, an item table with wrapped descriptions, subtotal, discount, one t…

### `overdue_report` (~62 tokens)

Overdue report

List every invoice not paid in full whose due date has passed, worst first, with days overdue and the amount, then a total per currency. Free. Use invoice_list for everything still open.

Input parameters:

- `as_of` (string): YYYY-MM-DD, defaults to today

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/mcp-invoice#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36
- 2026-09-03: 36
- 2026-09-02: 36

## Common questions

### What is the io.github.theluckystrike/invoice-pdf-billing-generator MCP server?

io.github.theluckystrike/invoice-pdf-billing-generator is an MCP server listed in the public MCP registry as io.github.theluckystrike/invoice-pdf-billing-generator. Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/invoice).

### Is the io.github.theluckystrike/invoice-pdf-billing-generator MCP server safe to use?

io.github.theluckystrike/invoice-pdf-billing-generator scores 82 out of 100 on VerifyMCP. 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-pdf-billing-generator MCP server expose?

io.github.theluckystrike/invoice-pdf-billing-generator exposes 13 tools: business_set, client_add, client_delete, client_list, invoice_create, and 8 more. Their descriptions and schemas cost roughly 1,854 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/invoice-pdf-billing-generator MCP server require authentication?

Yes. io.github.theluckystrike/invoice-pdf-billing-generator asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/invoice-pdf-billing-generator MCP server still maintained?

io.github.theluckystrike/invoice-pdf-billing-generator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/invoice
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/invoice
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/invoice
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/mcp-invoice.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/mcp-invoice.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-invoice-pdf-billing-generator/mcp-invoice