Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/subscription-manager-track-renewals

REMOTE · MCP.ZOVO.ONE

Track subscriptions and renewals from your AI chat: schedules, due dates, reminders, local data.

Available components

−13 this week 81 Trust /100

Last scanned (15 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability83
  • 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
  • Context-footprint check failed: tool/resource definitions use about 1926 tokens (~120/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management96
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every 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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 14 Nov 26 +1
    • Stability: 0.97 → pass security
  • 13 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: excellent → good functional
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://mcp.zovo.one/mcp/subscription-manager-track-renewals

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.zovo.one/mcp/subscription-manager-track-renewals Verified 200
http (plaintext) http://mcp.zovo.one/mcp/subscription-manager-track-renewals HTTPS enforced 301 https://mcp.zovo.one/mcp/subscription-manager-track-renewals
MCP tools · 14 exposed · ~1,703 tokens

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 →

Tool Tokens
forecast ~63

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.

NameTypeReqDescription
monthsinteger–Months ahead including this one, default 12

No output schema declared.

No examples provided.

invoice_generate_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.

NameTypeReqDescription
as_ofstring–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_runboolean–List what would be created without creating anything. Default false. One run creates at most 60 invoices, oldest period first
schedule_idstring–Only this schedule. Free and unlimited on every tier

No output schema declared.

No examples provided.

license_activate ~76

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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

license_status ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schedule_create ~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.

NameTypeReqDescription
anchor_dayinteger–Pro: bill on this day of month instead of the start date's day. 31 means the last day of every month
auto_generateboolean–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
clientstringyesClient name or id, as in the invoice server. Unknown names are created on the first generated invoice
currencystring–Defaults to your business default currency
due_daysinteger–Days until each invoice is due, defaults to your payment terms
end_datestring–YYYY-MM-DD, INCLUSIVE: an occurrence landing exactly on it is still generated
end_of_monthboolean–Pro: always bill on the last day of the month
every–yesHow 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…
itemsarrayyesThe line items billed every period
notesstring–Free text printed under the totals of every generated invoice
start_datestringyesYYYY-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_notestring–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 ~95

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.

NameTypeReqDescription
idstringyesSchedule 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 ~66

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.

NameTypeReqDescription
idstringyesSchedule id, or a client name

No output schema declared.

No examples provided.

schedule_history ~63

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

schedule_list ~57

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.

NameTypeReqDescription
statusstring––

No output schema declared.

No examples provided.

schedule_pause ~54

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

schedule_resume ~56

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

schedule_skip ~161

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.

NameTypeReqDescription
idstringyesSchedule id, or a client name
periodstringyesThe 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…
undoboolean–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 ~88

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.

NameTypeReqDescription
daysinteger–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 ~251

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.

NameTypeReqDescription
anchor_day––Pro
auto_generateboolean––
clientstring––
currencystring––
due_daysinteger––
end_datestring|null–null clears the end date
end_of_monthboolean–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…
idstringyes–
itemsarray––
notesstring––
start_datestring––
tax_notestring–Replace the tax reason carried onto every future generated invoice. Pass an empty string to clear it

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/subscription-manager-track-renewals MCP server?

io.github.theluckystrike/subscription-manager-track-renewals is a hosted endpoint at https://mcp.zovo.one/mcp/subscription-manager-track-renewals, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-subscription-manager-track-renewa 'https://mcp.zovo.one/mcp/subscription-manager-track-renewals'
Common questions

What is the io.github.theluckystrike/subscription-manager-track-renewals MCP server?

io.github.theluckystrike/subscription-manager-track-renewals is an MCP server listed in the public MCP registry as io.github.theluckystrike/subscription-manager-track-renewals. Track subscriptions and renewals from your AI chat: schedules, due dates, reminders, local data. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/subscription-manager-track-renewals).

Is the io.github.theluckystrike/subscription-manager-track-renewals MCP server safe to use?

io.github.theluckystrike/subscription-manager-track-renewals scores 81 out of 100 on VerifyMCP. 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/subscription-manager-track-renewals MCP server expose?

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

Does the io.github.theluckystrike/subscription-manager-track-renewals MCP server require authentication?

No. We connected to io.github.theluckystrike/subscription-manager-track-renewals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.theluckystrike/subscription-manager-track-renewals MCP server still maintained?

io.github.theluckystrike/subscription-manager-track-renewals is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.theluckystrike/subscription-manager-track-renewals MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/subscription-manager-track-renewals, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.