Overdue Invoice Reminder

Install

Works with Claude Desktop. Read the repository before you give any tool access to your data.

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

3 read · 5 write · 1 delete

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Downloaded binary

Tools (9)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• aging_summaryAging summary of what is owedread-only

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

• invoice_deleteDelete an invoice from the registercan change or delete data

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

• invoice_statusThe full state of one chased invoiceread-only

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

• letter_sentRecord 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.

• overdue_listList overdue invoicesread-only

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

Signals

Stars

2

Forks

0

Open issues

0

Last commit (this folder)

Oct 16, 2026 (13 days ago)

Last release

Oct 14, 2026 (15 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.theluckystrike/overdue-invoice-reminder

Version

0.22.5

Auth

API key

Packages

mcpb https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/dunning-letters.mcpb

License

MIT

Repository

github.com/theluckystrike/mcp-servers

Website

mcp.zovo.one/s/dunning-letters

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql