# io.github.theluckystrike/dunning (mcpb · statement-of-account.mcpb)

Write payment chasers at three levels from the invoices that are actually overdue.

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

## Components

- mcpb · `statement-of-account.mcpb`: 55/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-dunning/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-statement.md), [page](https://verifymcp.io/servers/theluckystrike-dunning/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-statement)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/statement-of-account.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-20.

- **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 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **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).
  - Context-footprint check failed: tool/resource definitions use about 1015 tokens (~112/item across 9 items; 8 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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/statement-of-account.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-19 (score 55, +1)

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

### 2026-09-17 (score 54, +1)

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

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

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

### 2026-09-14 (score 52, +3)

- [functional improvement] Stability: unverified → 0.23

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

First indexed and scored.

## MCP tools (8)

### `statement_build` (~136 tokens)

Build a statement of account

Build one client's statement of account for a period: opening balance, invoices issued, payments received, credit notes, deposits applied and closing balance, in minor units and formatted.

Input parameters:

- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `from` (string, required): First day of the period, YYYY-MM-DD. Everything dated before it becomes the opening balance
- `to` (string, required): Last day of the period, YYYY-MM-DD, inclusive

### `statement_aging` (~142 tokens)

Age the open invoices

Break what is owed into 0-30, 31-60, 61-90 and over 90 days past the invoice due date as at a chosen date, for one client or for every client, per currency. Free and unlimited.

Input parameters:

- `as_of` (string): Age the invoices as at this date, YYYY-MM-DD. Defaults to today
- `client` (string): One client id or name. Omit to age every client in the books
- `currency` (string): Only this currency. Omit for every currency, each aged separately
- `limit` (integer): Maximum invoice rows returned, default and ceiling 2000

### `statement_text` (~184 tokens)

Plain-text statement of account

Turn one client's statement into a plain-text ledger with every movement in date order, the opening and closing balances and a sign-off, ready to paste into an email.

Input parameters:

- `as_of` (string): Date printed on the statement, YYYY-MM-DD. Defaults to today
- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `from` (string, required): First day of the period, YYYY-MM-DD
- `greeting` (string): Opening line, default "Hello" and the client name
- `sign_off` (string): Closing line, default your business name from the shared profile
- `to` (string, required): Last day of the period, YYYY-MM-DD, inclusive

### `statement_pdf` (~189 tokens)

Render the statement of account as a PDF

Call this tool to write one client's A4 statement of account and return the file path. Titled STATEMENT OF ACCOUNT, every movement in date order, closing with the balance outstanding. Pro.

Input parameters:

- `as_of` (string): Date printed on the statement, YYYY-MM-DD. Defaults to today
- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `from` (string, required): First day of the period, YYYY-MM-DD
- `out_path` (string): Where to write the PDF; defaults to this server's data directory under pdf/. Use a .pdf path: the bytes written are always PDF
- `to` (string, required): Last day of the period, YYYY-MM-DD, inclusive

### `dunning_text` (~196 tokens)

Write a dunning letter

Write a payment chaser for one client at level 1 friendly, 2 firm or 3 final demand, listing every overdue invoice with its age and total, plus your bank details when the profile has them. Level 3 is Pro.

Input parameters:

- `as_of` (string): Age the invoices as at this date, YYYY-MM-DD. Defaults to today
- `client` (string, required): Client id from the invoice server, an exact client name, or a name containing this text
- `currency` (string): Only needed when the client has documents in more than one currency. Currencies are never added together
- `greeting` (string): Opening line, default "Hello" and the client name
- `level` (integer, required): 1 friendly reminder, 2 firm reminder, 3 final demand. Level 3 is Pro
- `sign_off` (string): Closing line, default your business name from the shared profile

### `statements_report` (~78 tokens)

What every client owes

Show what is outstanding across every client, totalled per currency and aged, with the oldest overdue invoice and the clients carrying it. Pro.

Input parameters:

- `as_of` (string): Age the invoices as at this date, YYYY-MM-DD. Defaults to today
- `limit` (integer): How many clients to list, worst first. Default 20

### `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-dunning/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-statement#diagnostics

## Score history

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

## Common questions

### What is the io.github.theluckystrike/dunning MCP server?

io.github.theluckystrike/dunning is an MCP server listed in the public MCP registry as io.github.theluckystrike/dunning. Write payment chasers at three levels from the invoices that are actually overdue. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/statement-of-account.mcpb).

### Is the io.github.theluckystrike/dunning MCP server safe to use?

io.github.theluckystrike/dunning scores 55 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/dunning MCP server expose?

io.github.theluckystrike/dunning exposes 8 tools: statement_build, statement_aging, statement_text, statement_pdf, dunning_text, and 3 more. Their descriptions and schemas cost roughly 990 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/dunning MCP server under?

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