Recurring Invoice Scheduler Subscription Billing Due Reminders is an MCP server with 14 tools an agent can call, among them forecast, invoice_generate_due, license_activate. It answers at https://mcp.zovo.one/mcp/recurring over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
forecast | 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. Inputs: months |
invoice_generate_due | 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. Inputs: as_of, schedule_id, dry_run |
license_activate | 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. Inputs: key |
license_status | 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. |
schedule_create | 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. Inputs: client, items, currency, every, start_date, end_date |
schedule_delete | 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. Inputs: id |
schedule_get | 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. Inputs: id |
schedule_history | 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. Inputs: id |
schedule_list | 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. Inputs: status |
schedule_pause | 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. Inputs: id |
schedule_resume | 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. Inputs: id |
schedule_skip | 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. Inputs: id, period, undo |
schedule_upcoming | 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. Inputs: days |
schedule_update | 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. Inputs: id, client, items, currency, every, start_date |
Every block below points at https://mcp.zovo.one/mcp/recurring. Pick your client and copy.
claude mcp add --transport http recurring-invoice-scheduler-subs https://mcp.zovo.one/mcp/recurring
{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.zovo.one/mcp/recurring"]
}
}
}{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
}{
"servers": {
"recurring-invoice-scheduler-subs": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
}{
"context_servers": {
"recurring-invoice-scheduler-subs": {
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
}{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"serverUrl": "https://mcp.zovo.one/mcp/recurring"
}
}
}{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
}name: Recurring Invoice Scheduler Subscription Billing Due Reminders
version: 0.0.1
schema: v1
mcpServers:
- name: Recurring Invoice Scheduler Subscription Billing Due Reminders
type: streamable-http
url: https://mcp.zovo.one/mcp/recurring{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"httpUrl": "https://mcp.zovo.one/mcp/recurring"
}
}
}{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
}{
"mcpServers": {
"recurring-invoice-scheduler-subs": {
"url": "https://mcp.zovo.one/mcp/recurring"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.zovo.one%2Fmcp%2Frecurring&type=streamable_http&id=recurring-invoice-scheduler-subs&name=Recurring%20Invoice%20Scheduler%20Subscription%20Billing%20Due%20Reminders
It answered our last check on 24 October 2026 in 77 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
14, as returned by the server's own tools/list on 21 September 2026: forecast, invoice_generate_due, license_activate, license_status, schedule_create, schedule_delete, schedule_get, schedule_history, and 6 more.
It answered our last check on 24 October 2026 in 77 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.zovo.one/mcp/recurring. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.theluckystrike. Endpoint host: mcp.zovo.one. ARD identifier: urn:air:io.github.theluckystrike:mcp:recurring-invoice-scheduler-subscription-billing-due-reminders.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.