io.github.theluckystrike/subscriptions

Est-ce que io.github.theluckystrike/subscriptions est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.theluckystrike/subscriptions » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 14 outils

• forecast≈ 158 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • months · integer · optionnel
    Months ahead including this one, default 12

  Exemple d'appel

  {"name": "forecast", "arguments": {"months": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• invoice_generate_due≈ 282 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • as_of · string · optionnel
    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 it twice creates nothing the second time
  • dry_run · boolean · optionnel
    List what would be created without creating anything. Default false. One run creates at most 60 invoices, oldest period first
  • schedule_id · string · optionnel
    Only this schedule. Free and unlimited on every tier

  Exemple d'appel

  {"name": "invoice_generate_due", "arguments": {"as_of": "texte", "dry_run": true, "schedule_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• license_activate≈ 167 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    License key from checkout, MCPL1.<payload>.<signature>

  Exemple d'appel

  {"name": "license_activate", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• license_status≈ 125 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "license_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_create≈ 882 tokens

  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.

  Paramètres, retour & exemple (12)

  Paramètres

  • every · ? · requis
    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 on the 28th/29th in February and back on the 31st in March
  • items · array · requis
    The line items billed every period
  • notes · string · optionnel
    Free text printed under the totals of every generated invoice
  • client · string · requis
    Client name or id, as in the invoice server. Unknown names are created on the first generated invoice
  • currency · string · optionnel
    Defaults to your business default currency
  • due_days · integer · optionnel
    Days until each invoice is due, defaults to your payment terms
  • end_date · string · optionnel
    YYYY-MM-DD, INCLUSIVE: an occurrence landing exactly on it is still generated
  • tax_note · string · optionnel
    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 generates, so a 0% retainer carries its reason on the document instead of only in the chat
  • anchor_day · integer · optionnel
    Pro: bill on this day of month instead of the start date's day. 31 means the last day of every month
  • start_date · string · requis
    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
  • end_of_month · boolean · optionnel
    Pro: always bill on the last day of the month
  • auto_generate · boolean · optionnel
    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

  Exemple d'appel

  {"name": "schedule_create", "arguments": {"every": "texte", "items": [], "client": "texte", "start_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_delete≈ 189 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    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

  Exemple d'appel

  {"name": "schedule_delete", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_get≈ 153 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Schedule id, or a client name

  Exemple d'appel

  {"name": "schedule_get", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_history≈ 146 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

  {"name": "schedule_history", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_list≈ 143 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel · active | paused

  Exemple d'appel

  {"name": "schedule_list", "arguments": {"status": "active"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_pause≈ 142 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

  {"name": "schedule_pause", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_resume≈ 142 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

  {"name": "schedule_resume", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_skip≈ 282 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    Schedule id, or a client name
  • undo · boolean · optionnel
    Remove a previous skip so the period becomes due again. Works only on a period that has not been invoiced. Default false
  • period · string · requis
    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 resumed schedule still back-bills the periods it missed, whereas a skipped period is closed for good

  Exemple d'appel

  {"name": "schedule_skip", "arguments": {"id": "texte", "period": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_upcoming≈ 183 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • days · integer · optionnel
    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

  Exemple d'appel

  {"name": "schedule_upcoming", "arguments": {"days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• schedule_update≈ 604 tokens

  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.

  Paramètres, retour & exemple (13)

  Paramètres

  • id · string · requis
  • every · ? · optionnel
    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 on the 28th/29th in February and back on the 31st in March
  • items · array · optionnel
  • notes · string · optionnel
  • client · string · optionnel
  • currency · string · optionnel
  • due_days · integer · optionnel
  • end_date · string|null · optionnel
    null clears the end date
  • tax_note · string · optionnel
    Replace the tax reason carried onto every future generated invoice. Pass an empty string to clear it
  • anchor_day · ? · optionnel
    Pro
  • start_date · string · optionnel
  • end_of_month · boolean · optionnel
    Pro
  • auto_generate · boolean · optionnel

  Exemple d'appel

  {"name": "schedule_update", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.zovo.one/mcp/subscriptions