# io.github.theluckystrike/billing-docs-credit-notes-purchase-orders (remote · mcp.zovo.one)

Credit notes against your invoices and purchase orders to suppliers, with VAT and A4 PDFs.

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

## Components

- remote · `mcp.zovo.one`: 83/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/mcp-billing-docs.md), [page](https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/mcp-billing-docs)
- mcpb · `billing-docs.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-billing-do.md), [page](https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-billing-do)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/billing-docs`
- 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**: 87/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).
  - Tool/resource definitions use about 1888 tokens (~104/item across 18 items; 16 tools + 2 resources), lean.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "credit_note_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 17 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/billing-docs-credit-notes-purchase… MCP server?

io.github.theluckystrike/billing-docs-credit-notes-purchase… is a hosted endpoint at https://mcp.zovo.one/mcp/billing-docs, 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-billing-docs-credit-notes-purchas 'https://mcp.zovo.one/mcp/billing-docs'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-billing-docs-credit-notes-purchas": {
      "url": "https://mcp.zovo.one/mcp/billing-docs"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-billing-docs-credit-notes-purchas": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/billing-docs"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-billing-docs-credit-notes-purchas]
url = "https://mcp.zovo.one/mcp/billing-docs"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-billing-docs-credit-notes-purchas": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/billing-docs",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-billing-docs-credit-notes-purchas --url 'https://mcp.zovo.one/mcp/billing-docs' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-billing-docs-credit-notes-purchas:
    url: "https://mcp.zovo.one/mcp/billing-docs"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-billing-docs-credit-notes-purchas": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/billing-docs"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-billing-docs-credit-notes-purchas -t streamable-http -u 'https://mcp.zovo.one/mcp/billing-docs'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-billing-docs-credit-notes-purchas": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/billing-docs"
    }
  }
}
```

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 83, +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 82, +57)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.30

### 2026-09-17 (score 25, −56)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Transport: pass → unverified
- [security regression] Stability: 0.23 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: fail → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-15 (score 81, +1)

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

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

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

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

- [security] Tool “purchase_order_create” 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 improvement] Schema quality: fail → pass
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

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

- [security] Tool “credit_note_text” 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] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_create” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_pdf” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_get” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_list” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_receive” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_delete” rewrote its description, which is the text the model reads
- [security] Tool “purchase_order_text” rewrote its description, which is the text the model reads
- [security] Tool “billing_docs_report” rewrote its description, which is the text the model reads
- [security] Tool “credit_note_create” rewrote its description, which is the text the model reads
- [security] Tool “credit_note_delete” rewrote its description, which is the text the model reads
- [security] Tool “credit_note_get” rewrote its description, which is the text the model reads
- [security] Tool “credit_note_list” rewrote its description, which is the text the model reads
- [security] Tool “credit_note_pdf” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0

## MCP tools (16)

### `credit_note_create` (~209 tokens)

Credit an invoice

Credit one invoice: the whole invoice, a GROSS amount_minor split over its VAT rates, or named lines. Amounts store negative, reusing the invoice's own rates. Free: 5 a month. Send it with credit_note_text.

Input parameters:

- `amount_minor` (integer): Credit this GROSS amount, VAT included, in minor units. Split across the invoice's VAT rates in proportion to each rate's share of the total
- `invoice` (string, required): The invoice number to credit, e.g. INV-2026-0001
- `issue_date` (string): YYYY-MM-DD, defaults to today in your business profile's timezone
- `lines` (array): Credit only these invoice lines. Leave out with amount_minor for a full credit note
- `notes` (string): Free text printed under the totals
- `reason` (string, required): Why the money is being given back, e.g. "returned goods" or "billed twice". Printed on the document

### `credit_note_list` (~109 tokens)

List credit notes

List credit notes newest first: id, invoice, client, basis, reason, currency and the NEGATIVE total, with the amount credited per currency. Filter by invoice, client or issue date range.

Input parameters:

- `client` (string): Only credit notes for clients whose name contains this text
- `from` (string): YYYY-MM-DD, earliest issue date
- `invoice` (string): Only credit notes issued against this invoice number
- `to` (string): YYYY-MM-DD, latest issue date

### `credit_note_get` (~81 tokens)

Show one credit note

Return one credit note in full by id or exact client name: every negated line, VAT lines, totals, the reason, and the invoice number and date it reverses. Reads only. Use credit_note_list for the ids.

Input parameters:

- `id` (string, required): Credit note id such as CN-2026-0001, or an exact client name

### `credit_note_pdf` (~108 tokens)

Render the credit note as a PDF

Call this tool to render one credit note as an A4 print-ready document and return a download link valid for one hour: the invoice layout titled CREDIT NOTE, with the invoice it reverses. Pro.

Input parameters:

- `id` (string, required): Credit note id such as CN-2026-0001
- `out_path` (string): Name for the downloaded file, e.g. acme-credit. Defaults to the document id; the document comes back as a download link valid for one hour

### `credit_note_text` (~122 tokens)

Plain-text credit note to paste into email

Turn a credit note into a plain-text summary to paste into an email: the negated line table, VAT lines, total, reason, and what now comes off the invoice. Also a .txt download link valid one hour. Free; credit_note_pdf writes the A4 document.

Input parameters:

- `greeting` (string): Opening line, default "Hello" plus the client name
- `id` (string, required): Credit note id such as CN-2026-0001
- `sign_off` (string): Closing line, default your business name from the shared profile

### `credit_note_delete` (~76 tokens)

Delete a credit note

Remove one credit note never posted to its invoice and never rendered, freeing that month's slot; the invoice becomes creditable again. One with a dependent is refused: issue a fresh note to reverse a sent one.

Input parameters:

- `id` (string, required): Credit note id such as CN-2026-0001, or an exact client name

### `purchase_order_create` (~271 tokens)

Raise a purchase order

Raise a purchase order to a supplier from items and return its PO number and totals. unit_price is in MAJOR units; currency, VAT and the buyer block come from the shared profile. Free: 5 documents a calendar month.

Input parameters:

- `currency` (string): Defaults to your business default currency
- `discount_percent` (number): Discount applied to every line, in percent
- `expected_delivery_date` (string): YYYY-MM-DD, when the goods or work are due
- `issue_date` (string): YYYY-MM-DD, defaults to today in your business profile's timezone
- `items` (array, required): What is being ordered
- `notes` (string): Free text printed under the totals, e.g. delivery address or terms
- `supplier` (string, required): Supplier name or client id. A name the invoice server already knows brings its address, email and VAT id onto the order
- `supplier_address` (string): Postal address for the SUPPLIER block, newlines allowed
- `supplier_email` (string): Only if the user gave it; otherwise the stored client's email is used
- `supplier_vat_id` (string): Supplier VAT / tax registration id
- `tax_rate` (number): VAT percent for lines with no rate of their own. Defaults to the business default

### `purchase_order_list` (~103 tokens)

List purchase orders

List purchase orders newest first: id, supplier, order and expected delivery dates, status open, partially_received or received, currency, total and received date. Filter by status, supplier or date range.

Input parameters:

- `from` (string): YYYY-MM-DD, earliest order date
- `status` (string): Default "all"
- `supplier` (string): Only orders to suppliers whose name contains this text
- `to` (string): YYYY-MM-DD, latest order date

### `purchase_order_get` (~76 tokens)

Show one purchase order

Return one purchase order in full by id or exact supplier name: buyer and supplier blocks, every line with unit price and VAT, totals, the delivery date, status and every receipt with its date and note.

Input parameters:

- `id` (string, required): Purchase order id such as PO-2026-0001, or an exact supplier name

### `purchase_order_pdf` (~107 tokens)

Render the purchase order as a PDF

Call this tool to render one purchase order as an A4 print-ready document and return a download link valid for one hour: the invoice layout titled PURCHASE ORDER, with the buyer and supplier. Pro.

Input parameters:

- `id` (string, required): Purchase order id such as PO-2026-0001
- `out_path` (string): Name for the downloaded file, e.g. acme-credit. Defaults to the document id; the document comes back as a download link valid for one hour

### `purchase_order_text` (~121 tokens)

Plain-text purchase order to paste into email

Turn a purchase order into a plain-text order to paste into an email: the line table, VAT lines, total, and a line asking the supplier to deliver by the date and quote the PO number. Also a .txt download link valid one hour. Free on every tier.

Input parameters:

- `greeting` (string): Opening line, default "Hello" plus the supplier name
- `id` (string, required): Purchase order id such as PO-2026-0001
- `sign_off` (string): Closing line, default your business name from the shared profile

### `purchase_order_receive` (~141 tokens)

Mark a purchase order received

Record that an order arrived. partial keeps it open and can be repeated, each receipt kept with its date and note; a full receipt closes it. An order already received, or a date before the order date, is refused.

Input parameters:

- `date` (string): YYYY-MM-DD, defaults to today
- `id` (string, required): Purchase order id such as PO-2026-0001
- `note` (string): What arrived, e.g. "8 of 10 units, 2 back-ordered"
- `partial` (boolean): True when only some of the order arrived. The order stays open and can be received again. Default false

### `purchase_order_delete` (~74 tokens)

Delete a purchase order

Remove one purchase order with nothing received and never rendered, freeing that month's slot. One with a receipt is refused, naming it. The PO number is never reissued. purchase_order_receive logs arrivals.

Input parameters:

- `id` (string, required): Purchase order id such as PO-2026-0001, or an exact supplier name

### `billing_docs_report` (~86 tokens)

Credited money and open orders

Over a date range: what was credited back per currency and against how many invoices, what is still on order per currency, and every open order past its delivery date with days late. Pro; the list tools are free.

Input parameters:

- `from` (string): YYYY-MM-DD, earliest document date to count
- `to` (string): YYYY-MM-DD, latest document date to count

### `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-billing-docs-credit-notes-purchase-orders/mcp-billing-docs#diagnostics

## Score history

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

## Common questions

### What is the io.github.theluckystrike/billing-docs-credit-notes-purchase… MCP server?

io.github.theluckystrike/billing-docs-credit-notes-purchase… is an MCP server listed in the public MCP registry as io.github.theluckystrike/billing-docs-credit-notes-purchase…. Credit notes against your invoices and purchase orders to suppliers, with VAT and A4 PDFs. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/billing-docs).

### Is the io.github.theluckystrike/billing-docs-credit-notes-purchase… MCP server safe to use?

io.github.theluckystrike/billing-docs-credit-notes-purchase… scores 83 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/billing-docs-credit-notes-purchase… MCP server expose?

io.github.theluckystrike/billing-docs-credit-notes-purchase… exposes 16 tools: credit_note_create, credit_note_list, credit_note_get, credit_note_pdf, credit_note_text, and 11 more. Their descriptions and schemas cost roughly 1,815 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/billing-docs-credit-notes-purchase… MCP server require authentication?

Yes. io.github.theluckystrike/billing-docs-credit-notes-purchase… 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/billing-docs-credit-notes-purchase… MCP server still maintained?

io.github.theluckystrike/billing-docs-credit-notes-purchase… 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/billing-docs
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/billing-docs
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/billing-docs
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/mcp-billing-docs.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/mcp-billing-docs.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-billing-docs-credit-notes-purchase-orders/mcp-billing-docs