# Theluckystrike Recurring Invoice Scheduler Subscription Billing Due Reminders MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Frecurring-invoice-scheduler-subscription-billing-due-reminders
Registry id: `mcp-registry/io.github.theluckystrike/recurring-invoice-scheduler-subscription-billing-due-reminders`
Status: live (checked 2026-11-22T17:58:18.393Z)

## Measurements (30 days)

- Uptime: 85.9%
- Checks: 3454
- Outages (90 days): 894

## Install

```json
{
  "mcpServers": {
    "theluckystrike-recurring-invoice-schedul": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/recurring"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http theluckystrike-recurring-invoice-schedul https://mcp.zovo.one/mcp/recurring
```

## Tools (14)

- `forecast`: Expected invoiced revenue per calendar month per currency from active schedules. Invoiced and skipped periods are excluded and paused schedules listed apart. Fr
- `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 w
- `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 
- `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 fr
- `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. Not
- `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 period
- `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 gen
- `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, skippe
- `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 sc
- `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,
- `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 wo
- `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 ref
- `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 l
- `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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
