Dunning Letters MCP Server

by theluckystrike Your server? Claim it

answering

Dunning Letters is answering right now. Last checked 2 min ago. It exposes 11 tools. Last commit 18 Sep 2026.

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

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

167 ms

Response time

average over 24h

Stars

last commit 18 Sep 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

17 Sep a tool changed version

Nothing serious here today

Today is the operative word: we check Dunning Letters every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add dunning-letters --transport http https://mcp.zovo.one/mcp/dunning-letters

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

invoice

invoice_delete

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.

invoice_register

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.

invoice_status

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.

letter

letter_render

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.

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

license

license_activate

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.

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.

aging

aging_summary

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

chase

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.

overdue

overdue_list

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.

payment

payment_record

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.zovo.one/mcp/dunning-letters	streamable-http	answering	121 ms	2 min ago

Alternatives to Dunning Letters

same job, measured the same way

Overdue Invoice Reminder

by theluckystrike

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

local only

Freelance Ops MCP

by nimish14

Freelance invoice ops MCP — overdue status, tone suggestion, and reminder drafts

28 installs/wk local only

Invoices Invoicing

by theluckystrike

Invoices and invoicing from your AI chat: PDF generation, numbering, VAT, overdue reports.

local only

Invoice PDF Billing Generator

by theluckystrike

Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.

13 tools answering

Invoice Generator

by theluckystrike

Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.

local only

Freelance Invoice

by theluckystrike

Create PDF invoices from your AI chat: clients, numbering, VAT, overdue reports. All data is local.

local only

Zencap

by zencap

Institutional financial data with SEC filing citations, for every AI agent. OAuth 2.1.

answering

Invoice Data Extraction

by invoicedataextraction

Invoices and other financial documents to rows: upload, say what to extract, read the rows.

answering

Dunning Letters — questions

Answers built from our own checks of this server.

What can Dunning Letters do?

It exposes 11 tools, read directly from the server on our last check. Among them: aging_summary, chase_today, invoice_delete, invoice_register, invoice_status, letter_render and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Dunning Letters mostly used for?

Its tools cluster around invoice, letter and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Dunning Letters working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 167 ms. The bar chart above shows every period we have measured.

How do I connect Dunning Letters?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Dunning Letters need an API key?

No. Dunning Letters completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Dunning Letters?

It answers our handshake in 167 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Dunning Letters open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.