McpStamp Dunning Letters

io.github.theluckystrike由 GitHub 帳號 theluckystrike 發布v0.23.0更新於 Nov 3, 2026

催收未付發票：提醒函、正式提醒函和最終通知函，以及每日催收清單。

AI 翻譯由 AI 模型根據下方的原文描述翻譯，可能有誤。

原文描述

Chase unpaid invoices: reminder, firm reminder and final notice letters, and a daily chase list.

已驗證Streamable HTTP可網頁執行效率與工作流金融

概覽

McpStamp Dunning Letters 的託管 MCP 服務（mcp.zovo.one）；無需登入；Streamable HTTP；11 個工具。

暫無 AI 概覽：以下資訊來自註冊中心條目和服務本身。

端點
mcp.zovo.one
最近檢查

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 McpStamp Dunning Letters，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.theluckystrike%2Fdunning-letters/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

README

Automated payment reminders for overdue invoices

[theluckystrike/mcp-dunning-letters MCP server]

In the official MCP Registry (io.github.theluckystrike/dunning-letters). Chase overdue invoices without losing the thread. Register an unpaid invoice, client, invoice reference, amount in integer cents, currency, due date, and the server runs the escalation ladder: reminder 1 (polite, due + 7 days), reminder 2 (firm, with the late fees note, due + 14), and the final notice (before-action wording, due + 21; the gaps are configurable per invoice). For each stage it generates the letter, as Markdown or as a self-contained printable HTML page. It records what you sent and when, lists everything overdue with days late and stage, ages the whole register into current/30/60/90+ buckets, and answers "what do I need to send today". Nothing is emailed or sent anywhere: this server produces the letter text, and sending it is your act.

Built by theluckystrike.

npm publish for @theluckystrike/mcp-dunning-letters is pending, so npx -y @theluckystrike/mcp-dunning-letters returns 404 today. Until then, a clone+build is the working path.

Install

Claude Desktop

macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:

json
{  "mcpServers": {    "dunning-letters": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-dunning-letters"]    }  }}

Claude Code

sh
claude mcp add dunning-letters -- npx -y @theluckystrike/mcp-dunning-letters

Cursor

~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.

Tools

toolwhat it does
invoice_registerStart chasing an unpaid invoice: client, reference, amount, currency, due date. Returns DUN-YYYY-NNNN and the three escalation dates
payment_recordRecord money received, full or partial. A part payment lowers what the next letter asks for; covering the balance closes the ladder
letter_renderGenerate the chase letter for the current stage -- reminder 1, reminder 2 or the final notice -- as Markdown or self-contained printable HTML. Nothing is emailed: you send the text it produces
letter_sentRecord that a letter actually went out, with its date, so the ladder advances. Letters go out in order
overdue_listEvery unpaid invoice past its due date: days late, outstanding, letters sent, what is due next, worst first
aging_summaryThe whole register in current/1-30/31-60/61-90/91+ buckets, counts and totals in integer cents, per currency
chase_todayThe day's chase list: which invoices cross an escalation threshold today, which letter to send each, what falls due next
invoice_statusOne chased invoice in full: payments, letters, schedule, next action
invoice_deleteDelete an invoice entered wrongly. The id is not reissued
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Unpaid invoices chased at once3Unlimited
All three letters, both formatsYesYes
Aging summary and the day's chase listYesYes
Late fee accrual in the lettersYesYes
Payment recording and historyYesYes

The cap is on how many chases run at once, never on the letters or the aging: three late payers taken from first reminder to final notice is a real chase list, and an invoice that gets paid frees its slot. What is metered is breadth, a fourth concurrent chase is a collections workload, not a freelancer's month.

Get Pro: https://mcp.zovo.one/buy/dunning-letters, $19 one-time for this server, or $39 for the bundle.

A measured insight

The ladder is anchored to the due date, not to the last letter, and the two drift apart exactly when chasing is going badly.

The worked chase in test/_client.mjs: USD 1,250.00 due 2026-06-01, gaps 7/14/21, so the letters fall due on 06-08, 06-15 and 06-22 whether or not anything was sent. If reminder 1 actually goes out late, say 06-20, twelve days after its date, a previous-letter-anchored ladder would push the final notice to 07-11. This one does not: 06-22 stands, because the client's obligation was fixed by the due date, not by when you got around to writing. Recording a sending moves only which stage is next; it never moves the schedule. The letters are also strictly sequential: an invoice 60 days late with nothing sent is still owed reminder 1, because a final notice that no polite letter preceded reads as a threat, not a chase.

The late fee is measured the same way, once: simple interest, pro-rata on a 30-day month, on the amount outstanding on the day the letter is written, rounded once to the minor unit. On the worked chase that is 125,000 minor units at 2% over 30 days late, 2,500 exactly, and after a 50,000 part payment it is 1,500 on the 75,000 that remains, so the final notice asks for 76,500 and no invented figure more.

Privacy

All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/dunning-letters/. Two files: invoices.json, counter.json. Nothing is sent anywhere, no account, no API key, no network call in this server at all, and the letters are rendered to text for you to send yourself; this server holds no mail credentials and wants none. License keys are verified offline.

Built by theluckystrike. https://github.com/theluckystrike

Frequently asked questions

Is there an MCP server for payment reminders or dunning letters?

Yes. The dunning-letters server at mcp.zovo.one automates accounts-receivable follow-up: tiered reminder sequences (friendly, firm, final), printable PDF letters, per-customer aging. Free tier, hosted remote endpoint.

How do I send payment reminders from Claude?

Connect https://mcp.zovo.one/mcp/dunning-letters and say: 'List overdue invoices and draft a firm reminder for Acme.' The letter follows the standard tier sequence and exports as PDF.

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

來源：servers/dunning-letters/README.md，提交 6535b33

工具

11

invoice_register

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.

輸入參數due必填gapsnoteclient必填issuedcurrency必填reference必填amount_minor必填duplicate_oklate_fee_percent_per_month

payment_record

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.

輸入參數datenoteinvoice必填amount_minor必填

letter_render

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.

輸入參數onstageformatinvoice必填

letter_sent

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.

輸入參數sentstageinvoice必填

overdue_list

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.

輸入參數onlimit

aging_summary

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

輸入參數on

chase_today

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.

輸入參數onwithin_days

invoice_status

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.

輸入參數oninvoice必填

invoice_delete

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.

輸入參數invoice必填

license_status

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

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.

輸入參數key必填

版本歷史

4
  1. v0.23.0最新Nov 3, 2026
  2. v0.22.6Oct 14, 2026
  3. v0.22.0Sep 17, 2026
  4. v0.21.0Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分