Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/dunning-letters

REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20

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

+4 this week 82 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability88
  • 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 1453 tokens (~111/item across 13 items; 11 tools + 2 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Install

How do I install the io.github.theluckystrike/dunning-letters MCP server?

io.github.theluckystrike/dunning-letters is a hosted endpoint at https://mcp.zovo.one/mcp/dunning-letters, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-dunning-letters 'https://mcp.zovo.one/mcp/dunning-letters'
// .cursor/mcp.json
{
  "mcpServers": {
    "theluckystrike-dunning-letters": {
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "theluckystrike-dunning-letters": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.theluckystrike-dunning-letters]
url = "https://mcp.zovo.one/mcp/dunning-letters"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-dunning-letters": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/dunning-letters",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add theluckystrike-dunning-letters --url 'https://mcp.zovo.one/mcp/dunning-letters' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  theluckystrike-dunning-letters:
    url: "https://mcp.zovo.one/mcp/dunning-letters"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "theluckystrike-dunning-letters": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}
# add to Vellum
assistant mcp add theluckystrike-dunning-letters -t streamable-http -u 'https://mcp.zovo.one/mcp/dunning-letters'
// mcp.json
{
  "mcpServers": {
    "theluckystrike-dunning-letters": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/dunning-letters"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 0
    • Server version: 0.21.0 → 0.22.0 functional
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 12 Sept 26 78

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/dunning-letters

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 2 Sept 2026 1 Dec 2026 ECDSA 256 ECDSA-SHA256 ef74739bd6e575bb13db69661e215324
SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zovo.one. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
zovo.one. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"

Bearer realm="mcp.zovo.one", error="invalid_token"
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.zovo.one/mcp/dunning-letters Verified 200
http (plaintext) http://mcp.zovo.one/mcp/dunning-letters HTTPS enforced 301 https://mcp.zovo.one/mcp/dunning-letters
MCP tools · 11 exposed · ~1,370 tokens

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 →

Tool Tokens
aging_summary ~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".

NameTypeReqDescription
onstringThe date to age against, YYYY-MM-DD. Default today

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
onstringThe date to run the list for, YYYY-MM-DD, e.g. to see what Monday will need. Default today
within_daysintegerHow far ahead to list letters coming due, default 7 days

No output schema declared.

No examples provided.

invoice_delete ~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.

NameTypeReqDescription
invoicestringyesThe chased invoice: its id (DUN-2026-0001) or its invoice reference

No output schema declared.

No examples provided.

invoice_register ~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.

NameTypeReqDescription
amount_minorintegeryesThe invoice amount in whole minor units (integer cents). 125000 is USD 1,250.00
clientstringyesWho owes the money, e.g. Acme Ltd
currencystringyesISO code the invoice was issued in
duestringyesThe date payment fell due, YYYY-MM-DD. The ladder is anchored to this date
duplicate_okbooleanRegister even though an identical invoice is already on the register. Default false
gapsarrayDays after the due date at which reminder 1, reminder 2 and the final notice fall due, strictly increasing. Default [7, 14, 21]
issuedstringThe date the invoice was issued, YYYY-MM-DD, for the letter's reference line
late_fee_percent_per_monthnumberLate payment interest your terms allow, percent per month, simple and pro-rata. When set, reminder 2 and the final notice state the accrued figure
notestring
referencestringyesThe invoice number being chased, e.g. INV-1042

No output schema declared.

No examples provided.

invoice_status ~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.

NameTypeReqDescription
invoicestringyesThe chased invoice: its id (DUN-2026-0001) or its invoice reference
onstringThe date to judge lateness against, YYYY-MM-DD. Default today

No output schema declared.

No examples provided.

letter_render ~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.

NameTypeReqDescription
formatstringmarkdown (default) or html: a self-contained printable page with no external anything
invoicestringyesThe chased invoice: its id (DUN-2026-0001) or its invoice reference
onstringThe letter's date, YYYY-MM-DD; late fees accrue to it and the final-notice deadline is 7 days after it. Default today
stagenumberRender 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 ~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.

NameTypeReqDescription
invoicestringyesThe chased invoice: its id (DUN-2026-0001) or its invoice reference
sentstringThe date it was sent, YYYY-MM-DD. Default today
stagenumberWhich letter went out. Default the lowest unsent stage

No output schema declared.

No examples provided.

license_activate ~76

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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

license_status ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

overdue_list ~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.

NameTypeReqDescription
limitintegerMaximum rows, default and ceiling 2000
onstringThe date to judge lateness against, YYYY-MM-DD. Default today

No output schema declared.

No examples provided.

payment_record ~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.

NameTypeReqDescription
amount_minorintegeryesWhat was received, in whole minor units
datestringThe date the money arrived, YYYY-MM-DD. Default today
invoicestringyesThe chased invoice: its id (DUN-2026-0001) or its invoice reference
notestringHow it was paid, e.g. Bank transfer, or what it was against

No output schema declared.

No examples provided.

Common questions

What is the io.github.theluckystrike/dunning-letters MCP server?

io.github.theluckystrike/dunning-letters is an MCP server listed in the public MCP registry as io.github.theluckystrike/dunning-letters. Chase overdue invoices: reminder 1, reminder 2, final notice, escalation dates, aging. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/dunning-letters).

Is the io.github.theluckystrike/dunning-letters MCP server safe to use?

io.github.theluckystrike/dunning-letters scores 82 out of 100 on VerifyMCP. 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 io.github.theluckystrike/dunning-letters MCP server expose?

io.github.theluckystrike/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,370 tokens of context every time the server is loaded.

Does the io.github.theluckystrike/dunning-letters MCP server require authentication?

Yes. io.github.theluckystrike/dunning-letters asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.github.theluckystrike/dunning-letters MCP server still maintained?

io.github.theluckystrike/dunning-letters is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.