io.github.theluckystrike/invoice-pdf-billing-generator
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 21
Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 14 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
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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-invoice-pdf-billing-generator 'https://mcp.zovo.one/mcp/invoice'
{
"mcpServers": {
"theluckystrike-invoice-pdf-billing-generator": {
"url": "https://mcp.zovo.one/mcp/invoice"
}
}
} {
"servers": {
"theluckystrike-invoice-pdf-billing-generator": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/invoice"
}
}
} [mcp_servers.theluckystrike-invoice-pdf-billing-generator] url = "https://mcp.zovo.one/mcp/invoice"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-invoice-pdf-billing-generator": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/invoice",
"enabled": true
}
}
} openclaw mcp add theluckystrike-invoice-pdf-billing-generator --url 'https://mcp.zovo.one/mcp/invoice' --transport streamable-http
mcp_servers:
theluckystrike-invoice-pdf-billing-generator:
url: "https://mcp.zovo.one/mcp/invoice" {
"McpServers": {
"theluckystrike-invoice-pdf-billing-generator": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/invoice"
}
}
} assistant mcp add theluckystrike-invoice-pdf-billing-generator -t streamable-http -u 'https://mcp.zovo.one/mcp/invoice'
{
"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.
Every 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 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.
- 18 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.
- 17 Sept 26 0
- Server version: 0.21.0 → 0.22.0 functional
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 11 Sept 26 +1
- 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 security
- Schema quality: good → excellent functional
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- 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 security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/invoice
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/invoice | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/invoice | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/invoice |
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 ~352
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.
| 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 | – | 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 | yes | 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 |
No output schema declared.
No examples provided.
client_add Add a client ~93
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.
| 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_delete Delete a client ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | Client name or id, exactly as client_list shows it |
No output schema declared.
No examples provided.
client_list List clients ~49
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
invoice_create Create an invoice ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
invoice_from_hours Invoice from hours ~405
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | yes | – |
| 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 | yes | – |
| issue_date | string | – | – |
| notes | string | – | – |
| rate | number | yes | 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 | – | – |
No output schema declared.
No examples provided.
invoice_get Get one invoice ~49
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).
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | – |
No output schema declared.
No examples provided.
invoice_list List invoices ~88
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.
| 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 ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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 |
No output schema declared.
No examples provided.
invoice_pdf Render invoice PDF ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 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… |
No output schema declared.
No examples provided.
license_activate Activate license ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
overdue_report Overdue report ~62
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.
| 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-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.