# io.github.theluckystrike/overdue-invoice-reminder (mcpb · dunning-letters.mcpb)

Overdue invoice chasers: reminder 1, reminder 2, the final notice, and the day's chase list.

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

## Components

- mcpb · `dunning-letters.mcpb`: 52/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-overdue-invoice-reminder/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-dunning-le.md), [page](https://verifymcp.io/servers/theluckystrike-overdue-invoice-reminder/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-dunning-le)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/dunning-letters.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**: 23/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **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).
  - Context-footprint check failed: tool/resource definitions use about 1394 tokens (~116/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% 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; "invoice_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 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/dunning-letters.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 52, +4)

- [functional improvement] Stability: unverified → 0.27

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

First indexed and scored.

## MCP tools (11)

### `invoice_register` (~313 tokens)

Register an unpaid invoice to chase

Start chasing an unpaid invoice: register the client, the invoice reference, the amount in integer cents, the currency and the due date, and get the three-letter escalation schedule (reminder 1, reminder 2, final notice) with the date each falls due. Free tier: 3 unpaid invoices chased at once.

Input parameters:

- `amount_minor` (integer, required): The invoice amount in whole minor units (integer cents). 125000 is USD 1,250.00
- `client` (string, required): Who owes the money, e.g. Acme Ltd
- `currency` (string, required): ISO code the invoice was issued in
- `due` (string, required): The date payment fell due, YYYY-MM-DD. The ladder is anchored to this date
- `duplicate_ok` (boolean): Register even though an identical invoice is already on the register. Default false
- `gaps` (array): Days after the due date at which reminder 1, reminder 2 and the final notice fall due, strictly increasing. Default [7, 14, 21]
- `issued` (string): The date the invoice was issued, YYYY-MM-DD, for the letter's reference line
- `late_fee_percent_per_month` (number): Late payment interest your terms allow, percent per month, simple and pro-rata. When set, reminder 2 and the final notice state the accrued figure
- `note` (string)
- `reference` (string, required): The invoice number being chased, e.g. INV-1042

### `payment_record` (~137 tokens)

Record a payment received

Record money received against a chased invoice, in whole MINOR units: a part payment lowers what is still chased, a payment that covers the balance closes the ladder and frees the free-tier slot. Returns the outstanding amount.

Input parameters:

- `amount_minor` (integer, required): What was received, in whole minor units
- `date` (string): The date the money arrived, YYYY-MM-DD. Default today
- `invoice` (string, required): The chased invoice: its id (DUN-2026-0001) or its invoice reference
- `note` (string): How it was paid, e.g. Bank transfer, or what it was against

### `letter_render` (~209 tokens)

Generate the chase letter for the current stage

Chase an unpaid invoice: generate the letter for the current stage of the ladder -- reminder 1 (polite), reminder 2 (firm, with the late fees note) or the final notice (before-action wording) -- as Markdown or as self-contained printable HTML. Nothing is emailed or sent anywhere: this server produces the letter text, and sending it is your act. Record the sending with letter_sent so the ladder advances.

Input parameters:

- `format` (string): markdown (default) or html: a self-contained printable page with no external anything
- `invoice` (string, required): The chased invoice: its id (DUN-2026-0001) or its invoice reference
- `on` (string): The letter's date, YYYY-MM-DD; late fees accrue to it and the final-notice deadline is 7 days after it. Default today
- `stage` (number): Render a specific stage instead of the one currently due, to preview or to re-issue a letter already sent

### `letter_sent` (~119 tokens)

Record that a letter was sent

Record that a chase letter was actually sent, with its date, so the ladder advances to the next stage. Letters go out in order: reminder 2 cannot be recorded before reminder 1. Returns what is due next and when.

Input parameters:

- `invoice` (string, required): The chased invoice: its id (DUN-2026-0001) or its invoice reference
- `sent` (string): The date it was sent, YYYY-MM-DD. Default today
- `stage` (number): Which letter went out. Default the lowest unsent stage

### `overdue_list` (~85 tokens)

List overdue invoices

Every unpaid invoice past its due date: how many days late, what is still owed, which letters have gone out, and what is due next and when. Sorted by days late, worst first.

Input parameters:

- `limit` (integer): Maximum rows, default and ceiling 2000
- `on` (string): The date to judge lateness against, YYYY-MM-DD. Default today

### `aging_summary` (~87 tokens)

Aging summary of what is owed

The aging summary across every unpaid invoice: current, 1-30, 31-60, 61-90 and 91+ day buckets, with counts and totals in integer cents, per currency. This is the answer to "how much am I owed, and how stale is it".

Input parameters:

- `on` (string): The date to age against, YYYY-MM-DD. Default today

### `chase_today` (~111 tokens)

What to chase today

The day's chase list: which invoices cross an escalation threshold today, which letter to send each and how long it has been waiting, what falls due in the next few days, and which invoices have had all three letters and need a decision outside this server.

Input parameters:

- `on` (string): The date to run the list for, YYYY-MM-DD, e.g. to see what Monday will need. Default today
- `within_days` (integer): How far ahead to list letters coming due, default 7 days

### `invoice_status` (~99 tokens)

The full state of one chased invoice

One chased invoice in full: what was billed, what has been paid and what is still owed, every letter sent with its date, the escalation schedule with each stage's state, and what happens next and when.

Input parameters:

- `invoice` (string, required): The chased invoice: its id (DUN-2026-0001) or its invoice reference
- `on` (string): The date to judge lateness against, YYYY-MM-DD. Default today

### `invoice_delete` (~79 tokens)

Delete an invoice from the register

Delete an invoice entered wrongly, by id or reference: the record, its payments and its letter history. The id is not reissued, so a gap in the DUN series is the record that a deletion happened.

Input parameters:

- `invoice` (string, required): The chased invoice: its id (DUN-2026-0001) or its invoice reference

### `license_status` (~54 tokens)

License status

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

### `license_activate` (~71 tokens)

Activate license

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

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-overdue-invoice-reminder/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-dunning-le#diagnostics

## Score history

- 2026-09-21: 52
- 2026-09-20: 52
- 2026-09-19: 48
- 2026-09-18: 48
- 2026-09-17: 48
- 2026-09-16: 48
- 2026-09-15: 48
- 2026-09-14: 48
- 2026-09-13: 48
- 2026-09-12: 48

## Common questions

### What is the io.github.theluckystrike/overdue-invoice-reminder MCP server?

io.github.theluckystrike/overdue-invoice-reminder is an MCP server listed in the public MCP registry as io.github.theluckystrike/overdue-invoice-reminder. Overdue invoice chasers: reminder 1, reminder 2, the final notice, and the day's chase list. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/dunning-letters.mcpb).

### Is the io.github.theluckystrike/overdue-invoice-reminder MCP server safe to use?

io.github.theluckystrike/overdue-invoice-reminder scores 52 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/overdue-invoice-reminder MCP server expose?

io.github.theluckystrike/overdue-invoice-reminder exposes 11 tools: invoice_register, payment_record, letter_render, letter_sent, overdue_list, and 6 more. Their descriptions and schemas cost roughly 1,364 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/overdue-invoice-reminder MCP server under?

io.github.theluckystrike/overdue-invoice-reminder 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/dunning-letters
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-overdue-invoice-reminder/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-dunning-le.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-overdue-invoice-reminder/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-dunning-le.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-overdue-invoice-reminder/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-dunning-le