McpStamp Dunning Letters
MCPB · DUNNING-LETTERS.MCPB · 2 COMPONENTS
Chase unpaid invoices: reminder, firm reminder and final notice letters, and a daily chase list.
Available components
Last scanned (20 hours ago)
Scores higher than 96% of MCPB servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 47 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1394 tokens (~116/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "invoice_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +57
- Provenance: unverified → fail ▼ security
- Stability: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.21.0 functional
- 31 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 29 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 24 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 16 Oct 26 0
- Package version: 0.22.0 → 0.22.5 functional
- 14 Oct 26 −55
- Stability: 0.87 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.87 → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: 0.84 → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Licence: MIT functional
- Package version: 0.22.0 → 0.22.5 functional
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 67 to 77. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/dunning-letters.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
aging_summary Aging summary of what is owed ~87
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".
| Name | Type | Req | Description |
|---|---|---|---|
| on | string | – | The date to age against, YYYY-MM-DD. Default today |
No output schema declared.
No examples provided.
chase_today What to chase today ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
invoice_delete Delete an invoice from the register ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | The chased invoice: its id (DUN-2026-0001) or its invoice reference |
No output schema declared.
No examples provided.
invoice_register Register an unpaid invoice to chase ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | The invoice amount in whole minor units (integer cents). 125000 is USD 1,250.00 |
| client | string | yes | Who owes the money, e.g. Acme Ltd |
| currency | string | yes | ISO code the invoice was issued in |
| due | string | yes | 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 | yes | The invoice number being chased, e.g. INV-1042 |
No output schema declared.
No examples provided.
invoice_status The full state of one chased invoice ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | 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 |
No output schema declared.
No examples provided.
letter_render Generate the chase letter for the current stage ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | markdown (default) or html: a self-contained printable page with no external anything |
| invoice | string | yes | 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 |
No output schema declared.
No examples provided.
letter_sent Record that a letter was sent ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~71
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~54
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
overdue_list List overdue invoices ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum rows, default and ceiling 2000 |
| on | string | – | The date to judge lateness against, YYYY-MM-DD. Default today |
No output schema declared.
No examples provided.
payment_record Record a payment received ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_minor | integer | yes | What was received, in whole minor units |
| date | string | – | The date the money arrived, YYYY-MM-DD. Default today |
| invoice | string | yes | 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 |
No output schema declared.
No examples provided.
How do I install the McpStamp Dunning Letters MCP server?
McpStamp Dunning Letters ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, fcef83dcba122d24ac1936b7ba8cd229b2eed345dc204f3696cc936064cd87af; the commands to do that are on this page. If it does not match, do not open it.
mcpb · dunning-letters.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
fcef83dcba122d24ac1936b7ba8cd229b2eed345dc204f3696cc936064cd87af
macOS / Linux
echo "fcef83dcba122d24ac1936b7ba8cd229b2eed345dc204f3696cc936064cd87af dunning-letters.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\dunning-letters.mcpb).Hash -eq "fcef83dcba122d24ac1936b7ba8cd229b2eed345dc204f3696cc936064cd87af"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the McpStamp Dunning Letters MCP server?
McpStamp Dunning Letters is an MCP server listed in the public MCP registry as io.github.theluckystrike/dunning-letters. Chase unpaid invoices: reminder, firm reminder and final notice letters, and a daily chase list. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/dunning-letters.mcpb).
Is the McpStamp Dunning Letters MCP server safe to use?
McpStamp Dunning Letters scores 62 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 McpStamp Dunning Letters MCP server expose?
McpStamp 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,364 tokens of context every time the server is loaded.
What licence is the McpStamp Dunning Letters MCP server under?
McpStamp Dunning Letters declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.