io.github.theluckystrike/subscriptions
MCPB · RECURRING.MCPB · SCANNED SEP 20
Recurring subscriptions billing: schedule once, auto-generate due invoice PDFs.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security22
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 157 of 157 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 63 of 157 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1536 tokens (~102/item across 15 items; 14 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · recurring.mcpb
Download bundleEvery 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 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.
- 18 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.
- 16 Sept 26 +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.
- 15 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 7 Sept 26 47
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 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/recurring.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 157 packages
| Packages resolved | 157 |
|---|---|
| Deprecated | 2 |
| Stale | 63 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~51
Expected invoiced revenue per calendar month per currency from every active schedule. Free covers 3 months ahead; Pro covers 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 ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
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 ~89
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.
| 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 ~45
The full stored record for one schedule: items, cadence, dates, rules and how many invoices it has generated.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Schedule id, or a client name |
No output schema declared.
No examples provided.
schedule_history Schedule history (Pro) ~39
The audit log for one schedule: every period it has generated, the invoice number, dates, amount and PDF path.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
schedule_list List schedules ~35
Every schedule with its cadence, per-period amount, next due date and status (active or paused).
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
schedule_pause Pause a schedule ~35
Stop a schedule from generating invoices without deleting it. Its history is kept and it can be resumed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
schedule_resume Resume a schedule ~45
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
schedule_skip Skip one period ~164
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.
| 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 ~84
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.
| 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 ~243
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.
| 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/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.