io.github.theluckystrike/recurring-invoice-scheduler-subscription-billing-due-reminders
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 1776 tokens (~111/item across 16 items; 14 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% 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; "schedule_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 15 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
How do I install the io.github.theluckystrike/recurring-invoice-scheduler-subscr… MCP server?
io.github.theluckystrike/recurring-invoice-scheduler-subscr… is a hosted endpoint at https://mcp.zovo.one/mcp/recurring, 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
claude mcp add --transport http theluckystrike-recurring-invoice-scheduler-subsc 'https://mcp.zovo.one/mcp/recurring'
{
"mcpServers": {
"theluckystrike-recurring-invoice-scheduler-subsc": {
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
} {
"servers": {
"theluckystrike-recurring-invoice-scheduler-subsc": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
} [mcp_servers.theluckystrike-recurring-invoice-scheduler-subsc] url = "https://mcp.zovo.one/mcp/recurring"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-recurring-invoice-scheduler-subsc": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/recurring",
"enabled": true
}
}
} openclaw mcp add theluckystrike-recurring-invoice-scheduler-subsc --url 'https://mcp.zovo.one/mcp/recurring' --transport streamable-http
mcp_servers:
theluckystrike-recurring-invoice-scheduler-subsc:
url: "https://mcp.zovo.one/mcp/recurring" {
"McpServers": {
"theluckystrike-recurring-invoice-scheduler-subsc": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/recurring"
}
}
} assistant mcp add theluckystrike-recurring-invoice-scheduler-subsc -t streamable-http -u 'https://mcp.zovo.one/mcp/recurring'
{
"mcpServers": {
"theluckystrike-recurring-invoice-scheduler-subsc": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Server version: 0.21.0 → 0.22.0 functional
- 15 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.
- 13 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.
- 11 Sept 26 +1
- Tool “schedule_history” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “schedule_update” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 +1
- Tool “forecast” rewrote its description, which is the text the model reads security
- Tool “schedule_skip” rewrote its description, which is the text the model reads security
- Tool “schedule_resume” rewrote its description, which is the text the model reads security
- Tool “schedule_pause” rewrote its description, which is the text the model reads security
- Tool “schedule_list” rewrote its description, which is the text the model reads security
- Tool “schedule_history” rewrote its description, which is the text the model reads security
- Tool “schedule_get” rewrote its description, which is the text the model reads security
- Tool “schedule_delete” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Tool “schedule_upcoming” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- “license_activate” reworded the description of “key” cosmetic
- Tool “schedule_history” changed its title: Schedule history (Pro) → Schedule history cosmetic
- 9 Sept 26 +40
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 70 functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- 3 Sept 26 36
First indexed and scored.
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/recurring
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/recurring | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/recurring | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/recurring |
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 →
forecast Revenue forecast ~63
Expected invoiced revenue per calendar month per currency from active schedules. Invoiced and skipped periods are excluded and paused schedules listed apart. Free: 3 months; Pro: up to 120.
| Name | Type | Req | Description |
|---|---|---|---|
| months | integer | – | Months ahead including this one, default 12 |
No output schema declared.
No examples provided.
invoice_generate_due Generate the invoices that are due ~161
Create a real invoice in the invoice server for every schedule occurrence on or before as_of that has not been invoiced yet, and render each PDF. Returns what was created, what was skipped and what is still due.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD, defaults to today. Every occurrence on or before this date that has not been invoiced is billed. Idempotent: one invoice per schedule per period, keyed by the occurrence date, so running… |
| dry_run | boolean | – | List what would be created without creating anything. Default false. One run creates at most 60 invoices, oldest period first |
| schedule_id | string | – | Only this schedule. Free and unlimited on every tier |
No output schema declared.
No examples provided.
license_activate Activate license ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status 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.
schedule_create Create a recurring invoice schedule ~457
Define a repeating invoice: a client, the line items, how often to bill, and when it starts and ends. Returns the schedule id, a summary and its next dates. Nothing is invoiced until invoice_generate_due runs.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_day | integer | – | Pro: bill on this day of month instead of the start date's day. 31 means the last day of every month |
| auto_generate | boolean | – | Marks the schedule for the monthly_billing_run prompt. Default false. Nothing runs in the background either way: invoices are created only when invoice_generate_due is called |
| client | string | yes | Client name or id, as in the invoice server. Unknown names are created on the first generated invoice |
| currency | string | – | Defaults to your business default currency |
| due_days | integer | – | Days until each invoice is due, defaults to your payment terms |
| end_date | string | – | YYYY-MM-DD, INCLUSIVE: an occurrence landing exactly on it is still generated |
| end_of_month | boolean | – | Pro: always bill on the last day of the month |
| every | – | yes | How often to bill: "weekly", "monthly", "quarterly", "yearly", or {days: 10}. Month steps keep the start date's day of month and clamp it to shorter months, so a schedule starting on the 31st bills o… |
| items | array | yes | The line items billed every period |
| notes | string | – | Free text printed under the totals of every generated invoice |
| start_date | string | yes | YYYY-MM-DD. The first invoice falls on this date, and for weekly/monthly/quarterly/yearly steps its day of month is the billing day for every later period |
| tax_note | string | – | Why this schedule bills the tax it bills, e.g. 'Reverse charge: VAT accounted for by the recipient, art. 196 Directive 2006/112/EC'. It is printed under the totals of EVERY invoice this schedule gene… |
No output schema declared.
No examples provided.
schedule_delete Delete a schedule ~95
Delete one schedule permanently. Invoices already generated stay in the invoice server and the history is kept. Re-creating it gives a NEW id, so its old periods count as unbilled. schedule_pause is reversible.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Schedule id, or a client name. Deletion is permanent; re-creating the same schedule afterwards gives it a NEW id, so its old periods count as unbilled again |
No output schema declared.
No examples provided.
schedule_get Get one schedule ~66
Return one schedule in full by id or client: items, cadence, dates, due days, anchor rules, notes, per-period amount, next due date and how many invoices it generated. schedule_history is the log.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Schedule id, or a client name |
No output schema declared.
No examples provided.
schedule_history Schedule history ~63
The audit log for one schedule id, oldest first: period, invoice number, issue and due dates, amount, PDF path, and whether that invoice is unpaid, paid, skipped or since deleted. schedule_list finds the id. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
schedule_list List schedules ~57
List schedules: id, client, cadence, per-period amount and currency, start and end dates, status, next due date and auto_generate. Filter by status; a paused schedule reports no next due date.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
schedule_pause Pause a schedule ~54
Stop one schedule generating invoices without deleting it; invoice_generate_due and forecast skip it. Its periods keep falling due and resuming back-bills them, so use schedule_skip to drop just one.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
schedule_resume Resume a schedule ~56
Make a paused schedule active again. Every period missed while it was paused is still due and the next invoice_generate_due creates them all. Refused when it would pass the free tier's 3 active.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
schedule_skip Skip one period ~161
Close ONE occurrence for good without pausing the schedule, reporting what will not be billed. period must be a real occurrence of it. An invoiced period is refused; undo reopens a skip.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Schedule id, or a client name |
| period | string | yes | The occurrence date to skip, YYYY-MM-DD, exactly as it appears in schedule_upcoming or forecast. This is the answer to "pause this client for October": schedule_pause stops the whole schedule and a r… |
| undo | boolean | – | Remove a previous skip so the period becomes due again. Works only on a period that has not been invoiced. Default false |
No output schema declared.
No examples provided.
schedule_upcoming What falls due soon ~88
Table every occurrence of every ACTIVE schedule due in the next N days (30 default), with its amount and the invoice due date, plus a total per currency. Free lists the first 3 in your horizon.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days ahead, default 30. The free tier honours the horizon you ask for and lists the first 3 occurrences in it; Pro lists them all |
No output schema declared.
No examples provided.
schedule_update Update a schedule ~251
Change one schedule by id: client, items, currency, cadence, dates, due_days, notes or auto_generate. Only the fields you pass change. Periods already invoiced are never re-issued, so a new amount applies to future ones.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_day | – | – | Pro |
| auto_generate | boolean | – | – |
| client | string | – | – |
| currency | string | – | – |
| due_days | integer | – | – |
| end_date | string|null | – | null clears the end date |
| end_of_month | boolean | – | Pro |
| every | – | – | How often to bill: "weekly", "monthly", "quarterly", "yearly", or {days: 10}. Month steps keep the start date's day of month and clamp it to shorter months, so a schedule starting on the 31st bills o… |
| id | string | yes | – |
| items | array | – | – |
| notes | string | – | – |
| start_date | string | – | – |
| tax_note | string | – | Replace the tax reason carried onto every future generated invoice. Pass an empty string to clear it |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/recurring-invoice-scheduler-subscr… MCP server?
io.github.theluckystrike/recurring-invoice-scheduler-subscr… is an MCP server listed in the public MCP registry as io.github.theluckystrike/recurring-invoice-scheduler-subscr…. Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/recurring).
Is the io.github.theluckystrike/recurring-invoice-scheduler-subscr… MCP server safe to use?
io.github.theluckystrike/recurring-invoice-scheduler-subscr… 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/recurring-invoice-scheduler-subscr… MCP server expose?
io.github.theluckystrike/recurring-invoice-scheduler-subscr… exposes 14 tools: schedule_create, schedule_list, schedule_get, schedule_update, schedule_pause, and 9 more. Their descriptions and schemas cost roughly 1,703 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/recurring-invoice-scheduler-subscr… MCP server require authentication?
Yes. io.github.theluckystrike/recurring-invoice-scheduler-subscr… 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/recurring-invoice-scheduler-subscr… MCP server still maintained?
io.github.theluckystrike/recurring-invoice-scheduler-subscr… 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.