# io.github.theluckystrike/subscriptions (mcpb · recurring.mcpb)

Recurring subscriptions billing: schedule once, auto-generate due invoice PDFs.

- Trust score: 53/100 (low)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- mcpb · `recurring.mcpb`: 53/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-subscriptions/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-recurring.md), [page](https://verifymcp.io/servers/theluckystrike-subscriptions/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-recurring)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/recurring.mcpb`
- Version: `0.21.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 22/100
  - Malware scan not yet available for this package.
  - Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 63 of 157 dependencies flagged as unhealthy (2 deprecated).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 13 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1536 tokens (~102/item across 15 items; 14 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

- Download bundle: `https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/recurring.mcpb`

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 53, +1)

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

### 2026-09-18 (score 52, +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.

### 2026-09-16 (score 51, +1)

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

### 2026-09-15 (score 50, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-07 (score 47)

First indexed and scored.

## MCP tools (14)

### `schedule_create` (~457 tokens)

Create a recurring invoice schedule

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.

Input parameters:

- `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, required): 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` (required): 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, required): The line items billed every period
- `notes` (string): Free text printed under the totals of every generated invoice
- `start_date` (string, required): 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…

### `schedule_list` (~35 tokens)

List schedules

Every schedule with its cadence, per-period amount, next due date and status (active or paused).

Input parameters:

- `status` (string)

### `schedule_get` (~45 tokens)

Get one schedule

The full stored record for one schedule: items, cadence, dates, rules and how many invoices it has generated.

Input parameters:

- `id` (string, required): Schedule id, or a client name

### `schedule_update` (~243 tokens)

Update a schedule

Change a schedule's client, items, currency, cadence, dates, due days, notes or auto_generate flag. Periods already invoiced are never re-issued, so changing the amount affects future invoices only.

Input parameters:

- `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, required)
- `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

### `schedule_pause` (~35 tokens)

Pause a schedule

Stop a schedule from generating invoices without deleting it. Its history is kept and it can be resumed.

Input parameters:

- `id` (string, required)

### `schedule_resume` (~45 tokens)

Resume a schedule

Make a paused schedule active again. Periods that fell due while it was paused are still due and will be created by the next invoice_generate_due.

Input parameters:

- `id` (string, required)

### `schedule_delete` (~89 tokens)

Delete a schedule

Remove a schedule. Invoices it already generated stay in the invoice server untouched and its generation history is kept as an audit trail. Returns the client and how many invoices and history rows remain.

Input parameters:

- `id` (string, required): 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

### `schedule_skip` (~164 tokens)

Skip one period

Skip a single occurrence of a schedule without pausing it: no invoice is ever created for that period, and every other period bills as normal. Returns the amount that will not be billed and how to undo it.

Input parameters:

- `id` (string, required): Schedule id, or a client name
- `period` (string, required): 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

### `schedule_upcoming` (~84 tokens)

What falls due soon

Table of every schedule occurrence falling due in the next N days, with the amount per occurrence and the total per currency. Free lists the first 3 occurrences in the horizon you ask for.

Input parameters:

- `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

### `invoice_generate_due` (~161 tokens)

Generate the invoices that are 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.

Input parameters:

- `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

### `schedule_history` (~39 tokens)

Schedule history (Pro)

The audit log for one schedule: every period it has generated, the invoice number, dates, amount and PDF path.

Input parameters:

- `id` (string, required)

### `forecast` (~51 tokens)

Revenue forecast

Expected invoiced revenue per calendar month per currency from every active schedule. Free covers 3 months ahead; Pro covers up to 120.

Input parameters:

- `months` (integer): Months ahead including this one, default 12

### `license_status` (~23 tokens)

License status

Show whether this server runs in free or Pro mode and where to upgrade.

### `license_activate` (~42 tokens)

Activate license

Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.

Input parameters:

- `key` (string, required): License key from the checkout confirmation page

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/theluckystrike-subscriptions/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-recurring#diagnostics

## Score history

- 2026-09-20: 53
- 2026-09-19: 52
- 2026-09-18: 52
- 2026-09-17: 51
- 2026-09-16: 51
- 2026-09-15: 50
- 2026-09-14: 47
- 2026-09-13: 47
- 2026-09-12: 47
- 2026-09-11: 47
- 2026-09-10: 47
- 2026-09-09: 47
- 2026-09-08: 47
- 2026-09-07: 47

## Common questions

### What is the io.github.theluckystrike/subscriptions MCP server?

io.github.theluckystrike/subscriptions is an MCP server listed in the public MCP registry as io.github.theluckystrike/subscriptions. Recurring subscriptions billing: schedule once, auto-generate due invoice PDFs. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/recurring.mcpb).

### Is the io.github.theluckystrike/subscriptions MCP server safe to use?

io.github.theluckystrike/subscriptions scores 53 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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/subscriptions MCP server expose?

io.github.theluckystrike/subscriptions exposes 14 tools: schedule_create, schedule_list, schedule_get, schedule_update, schedule_pause, and 9 more. Their descriptions and schemas cost roughly 1,513 tokens of context every time the server is loaded.

### What licence is the io.github.theluckystrike/subscriptions MCP server under?

io.github.theluckystrike/subscriptions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/recurring
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-subscriptions/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-recurring.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-subscriptions/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-recurring.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-subscriptions/https-github-com-theluckystrike-mcp-servers-releases-download-v0-21-0-recurring