# io.github.theluckystrike/credit-note (mcpb · billing-docs.mcpb)

Credit notes on your invoices: the whole invoice, an amount or named lines, VAT reused.

- Trust score: 54/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- mcpb · `billing-docs.mcpb`: 54/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-credit-note/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-billing-do.md), [page](https://verifymcp.io/servers/theluckystrike-credit-note/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-billing-do)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/billing-docs.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

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. 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-21.

- **Supply Chain Security**: 22/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 63 of 157 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 14 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/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 1619 tokens (~95/item across 17 items; 16 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/billing-docs.mcpb`

## 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 54, +1)

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

### 2026-09-18 (score 53, +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-16 (score 52, +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-15 (score 51, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 48)

First indexed and scored.

## MCP tools (16)

### `credit_note_create` (~198 tokens)

Credit an invoice

Issue a credit note against one invoice: the whole invoice, a gross amount, or named lines with quantities. Line totals are stored negative in minor units and the invoice's VAT rates are reused.

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` (~96 tokens)

List credit notes

Every credit note with its invoice, client, reason and negative total. Filter by invoice number, by client or by 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` (~65 tokens)

Show one credit note

The full stored record for one credit note: every negated line, the VAT lines, the totals, the reason and the invoice it was issued against.

Input parameters:

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

### `credit_note_pdf` (~89 tokens)

Render the credit note as a PDF

Call this tool to write the A4 PDF of one credit note and return the file path. The invoice layout, titled CREDIT NOTE and carrying the invoice number it reverses. Pro.

Input parameters:

- `id` (string, required): Credit note id such as CN-2026-0001
- `out_path` (string): Where to write the file. Defaults to the billing-docs data directory under pdf/

### `credit_note_text` (~106 tokens)

Plain-text credit note to paste into email

Turn a credit note into a plain-text summary with the negated line table, the VAT lines, the total and the invoice it reverses, ready to paste into an email. Free on every tier.

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` (~74 tokens)

Delete a credit note

Remove a credit note that was never posted to its invoice and never rendered to a file: the invoice becomes creditable again and the free monthly document slot comes back. One with a dependent is refused.

Input parameters:

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

### `purchase_order_create` (~261 tokens)

Raise a purchase order

Order from a supplier: line items with quantity and unit price in minor units, VAT, a currency and an expected delivery date. You are the buyer, from the shared business profile.

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` (~97 tokens)

List purchase orders

Every purchase order with its supplier, total, expected delivery date and status (open, partially received or received). Filter by status, by supplier or by order 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` (~71 tokens)

Show one purchase order

The full stored record for one purchase order: the buyer and supplier blocks, every line with its unit price and VAT, the totals, the expected delivery date and what has been received.

Input parameters:

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

### `purchase_order_pdf` (~92 tokens)

Render the purchase order as a PDF

Call this tool to write the A4 PDF of one purchase order and return the file path. The invoice layout, titled PURCHASE ORDER, with the buyer, the supplier and the delivery date. Pro.

Input parameters:

- `id` (string, required): Purchase order id such as PO-2026-0001
- `out_path` (string): Where to write the file. Defaults to the billing-docs data directory under pdf/

### `purchase_order_text` (~105 tokens)

Plain-text purchase order to paste into email

Turn a purchase order into a plain-text summary with the line table, the VAT lines, the total and the delivery date, ready to paste into an email to the supplier. 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` (~133 tokens)

Mark a purchase order received

Record that a purchase order arrived, in full or in part. A partial receipt keeps the order open and is kept on the record with its date and note; a full receipt closes it.

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` (~71 tokens)

Delete a purchase order

Remove a purchase order with nothing received against it that was never rendered to a file: the free monthly document slot comes back. An order with a receipt is refused, naming that receipt.

Input parameters:

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

### `billing_docs_report` (~75 tokens)

Credited money and open orders

What has been credited back per currency, against how many invoices, and what is still on order per currency, with the purchase orders whose delivery date has passed. Pro.

Input parameters:

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

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-credit-note/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-billing-do#diagnostics

## Score history

- 2026-09-21: 54
- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 51
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48
- 2026-09-11: 48
- 2026-09-10: 48
- 2026-09-09: 48
- 2026-09-08: 48
- 2026-09-07: 48

## Common questions

### What is the io.github.theluckystrike/credit-note MCP server?

io.github.theluckystrike/credit-note is an MCP server listed in the public MCP registry as io.github.theluckystrike/credit-note. Credit notes on your invoices: the whole invoice, an amount or named lines, VAT reused. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/billing-docs.mcpb).

### Is the io.github.theluckystrike/credit-note MCP server safe to use?

io.github.theluckystrike/credit-note scores 54 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/credit-note MCP server expose?

io.github.theluckystrike/credit-note 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,598 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/credit-note MCP server under?

io.github.theluckystrike/credit-note declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/billing-docs
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-credit-note/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-billing-do.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-credit-note/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-billing-do.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-credit-note/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-billing-do