# io.github.theluckystrike/dunning-letters (remote · mcp.zovo.one)

Chase overdue invoices: reminder 1, reminder 2, final notice, escalation dates, aging.

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

## Components

- remote · `mcp.zovo.one`: 84/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-dunning-letters/mcp-dunning-letters.md), [page](https://verifymcp.io/servers/theluckystrike-dunning-letters/mcp-dunning-letters)
- mcpb · `dunning-letters.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/theluckystrike-dunning-letters/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-dunning-le.md), [page](https://verifymcp.io/servers/theluckystrike-dunning-letters/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-dunning-le)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/dunning-letters`
- 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-21.

- **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**: 88/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 1453 tokens (~111/item across 13 items; 11 tools + 2 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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

### How do I install the io.github.theluckystrike/dunning-letters MCP server?

io.github.theluckystrike/dunning-letters is a hosted endpoint at https://mcp.zovo.one/mcp/dunning-letters, 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-dunning-letters 'https://mcp.zovo.one/mcp/dunning-letters'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-dunning-letters": {
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-dunning-letters": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-dunning-letters]
url = "https://mcp.zovo.one/mcp/dunning-letters"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-dunning-letters": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/dunning-letters",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-dunning-letters --url 'https://mcp.zovo.one/mcp/dunning-letters' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-dunning-letters:
    url: "https://mcp.zovo.one/mcp/dunning-letters"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-dunning-letters": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-dunning-letters -t streamable-http -u 'https://mcp.zovo.one/mcp/dunning-letters'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-dunning-letters": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
```

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-21 (score 84, +2)

- [security] Tool “invoice_delete” is now declared destructive
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.

### 2026-09-20 (score 82, +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-18 (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-17 (score 80, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (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-14 (score 79, +1)

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

### 2026-09-13 (score 78, 0)

- [functional improvement] Stability: unverified → 0.03

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

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` (~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-dunning-letters/mcp-dunning-letters#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78

## Common questions

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

io.github.theluckystrike/dunning-letters is an MCP server listed in the public MCP registry as io.github.theluckystrike/dunning-letters. Chase overdue invoices: reminder 1, reminder 2, final notice, escalation dates, aging. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/dunning-letters).

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

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

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

### Does the io.github.theluckystrike/dunning-letters MCP server require authentication?

Yes. io.github.theluckystrike/dunning-letters 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/dunning-letters MCP server still maintained?

io.github.theluckystrike/dunning-letters is still listed as active in the MCP registry. We last reached this channel on 21 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/dunning-letters
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/dunning-letters
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/dunning-letters
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-dunning-letters/mcp-dunning-letters.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-dunning-letters/mcp-dunning-letters.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-dunning-letters/mcp-dunning-letters