Dunning Letters MCP server

• aging_summaryFree

  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_todayFree

  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.

• invoice_deletewrite actionFree

  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_registerFree

  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_statusFree

  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_renderFree

  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_sentFree

  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_activateFree

  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_statusFree

  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.

• overdue_listFree

  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_recordFree

  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.

• –Code scanpackage could not be scannedn/a
• Live reliabilityremote reachable in 148ms20/20
• Tool poisoning11 tool descriptions checked15/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 1 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Grade history

• 2026-09-19restoreC → Ascore 88

Dunning Letters: common questions

Is Dunning Letters MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Dunning Letters safety report

How do I install Dunning Letters?

It runs remotely at mcp.zovo.one. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Dunning Letters need an API key?

Yes. The registry entry asks for MCP_LICENSE_KEY, Authorization.

Is Dunning Letters maintained?

The last commit was in the last day (2026-09-19). The latest release is v0.22.0.

Is Dunning Letters up?

100% of our last 3 checks got an answer. We check remote servers about four times a day.