mcp-registry/io.github.theluckystrike/dunning · v0.22.6
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 15:25 UTC, the Theluckystrike Dunning MCP server is degraded with a Glimind reliability score of 61/100 (grade C). Over the last 30 days it answered 81.3% of Glimind's liveness checks. It had 457 outages in 90 days, with a median recovery of 20 minutes.
Write payment chasers at three levels from the invoices that are actually overdue.
Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/dunning
Up 67.7% of the time over the last 30 days; median recovery 20 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 14 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.theluckystrike/dunning"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.theluckystrike/dunning"}) over MCP.
statement_text ~376 tokensdunning_text ~361 tokensstatement_pdf ~349 tokensstatement_build ~274 tokensstatement_aging ~242 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fdunning?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fdunning?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.theluckystrike%2Fdunning.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3595e96a8ffe7fc8…, first seen 2026-11-06, included at leaf 178609 of 384,260. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable other servers · most reliable security servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 15:25 UTC, the Theluckystrike Dunning MCP server is degraded with a Glimind reliability score of 61/100 (grade C). Over the last 30 days it answered 81.3% of Glimind's liveness checks. It had 457 outages in 90 days, with a median recovery of 20 minutes.
Theluckystrike Dunning MCP server advertises 8 tools, including dunning_text, license_activate, license_status, statement_aging, statement_build.
Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/dunning
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.