Skip to content

subscription-manager-track-renewals MCP server

io.github.theluckystrike/subscription-manager-track-renewalstheluckystrikestreamable-httpv0.23.1Scanned

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

14 tools: 1 can delete or cancel things, 12 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 12 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the subscription-manager-track-renewals MCP server can do

The subscription-manager-track-renewals MCP server is published by the GitHub account theluckystrike. It has 14 tools. It can delete or cancel things (1 tool: schedule_delete) and create or change data (12 tools: schedule_create, schedule_list, schedule_get, schedule_update and 8 more). 1 tool only reads.

1 tool brings in text other people can write (license_status).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.23.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 1Claude Code: deny
  • schedule_deleteDelete one schedule permanently.No findings

    Why it is in this group

    • The name "schedule_delete" says "schedule": a word for a change.
    • The description's first verb is "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 12Claude Code: ask
  • forecastExpected invoiced revenue per calendar month per currency from active schedules.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • invoice_generate_dueCreate 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.No findings

    Why it is in this group

    • The name "invoice_generate_due" says "generate": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_createDefine a repeating invoice: a client, the line items, how often to bill, and when it starts and ends.No findings

    Why it is in this group

    • The name "schedule_create" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_getReturn 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.1 finding

    Why it is in this group

    • The name "schedule_get" says "schedule": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "schedule_get" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "schedule_get" says "schedule": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • schedule_historyThe 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.No findings

    Why it is in this group

    • The name "schedule_history" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_listList schedules: id, client, cadence, per-period amount and currency, start and end dates, status, next due date and auto_generate.1 finding

    Why it is in this group

    • The name "schedule_list" says "schedule": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "schedule_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "schedule_list" says "schedule": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • schedule_pauseStop one schedule generating invoices without deleting it; invoice_generate_due and forecast skip it.No findings

    Why it is in this group

    • The name "schedule_pause" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_resumeMake a paused schedule active again.No findings

    Why it is in this group

    • The name "schedule_resume" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_skipClose ONE occurrence for good without pausing the schedule, reporting what will not be billed.No findings

    Why it is in this group

    • The name "schedule_skip" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_upcomingTable 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.No findings

    Why it is in this group

    • The name "schedule_upcoming" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_updateChange one schedule by id: client, items, currency, cadence, dates, due_days, notes or auto_generate.No findings

    Why it is in this group

    • The name "schedule_update" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • license_statusReport 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.Reads text others writeNo findings

    Why it is in this group

    • The name "license_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/subscription-manager-track-renewals
Authorization servers
https://mcp.zovo.one
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (1 destructive, 12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zovo.one/mcp/subscription-manager-track-renewals: tools/list returned 14 tools to an anonymous client, including schedule_delete (destructive), schedule_create (write), schedule_list (write), schedule_get (write), schedule_update (write) and 8 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 13
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/subscription-manager-track-renewals
  3. Oct 29, 2026
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 13 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "schedule_list" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "schedule_list" says "schedule": a word for a change.

    What this check looks for
  • The server marks "schedule_get" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "schedule_get" says "schedule": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 429 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 13 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 429 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 13
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/subscription-manager-track-renewals.View diff
    • RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/subscription-manager-track-renewals
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 429; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 13 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 429
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 13 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.23.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http subscription-manager-track-renewals https://mcp.zovo.one/mcp/subscription-manager-track-renewals --header 'Authorization: <your-authorization>'
claude mcp add --transport http subscription-manager-track-renewals https://mcp.zovo.one/mcp/subscription-manager-track-renewals --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__subscription-manager-track-renewals__license_status"
    ],
    "ask": [
      "mcp__subscription-manager-track-renewals__schedule_create",
      "mcp__subscription-manager-track-renewals__schedule_list",
      "mcp__subscription-manager-track-renewals__schedule_get",
      "mcp__subscription-manager-track-renewals__schedule_update",
      "mcp__subscription-manager-track-renewals__schedule_pause",
      "mcp__subscription-manager-track-renewals__schedule_resume",
      "mcp__subscription-manager-track-renewals__schedule_skip",
      "mcp__subscription-manager-track-renewals__schedule_upcoming",
      "mcp__subscription-manager-track-renewals__invoice_generate_due",
      "mcp__subscription-manager-track-renewals__schedule_history",
      "mcp__subscription-manager-track-renewals__forecast",
      "mcp__subscription-manager-track-renewals__license_activate"
    ],
    "deny": [
      "mcp__subscription-manager-track-renewals__schedule_delete"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as subscription-manager-track-renewals. Review it before you use it.

Capability tags behind 1 rule
  • mcp__subscription-manager-track-renewals__license_status untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/subscription-manager-track-renewals/verify?hash=2b16eaf64aae536b92277479c369382cedd4800308020d8f18c32b935a6ecd68" | jq -e '.changed == false'

Pinned hash 2b16eaf64aae, from Nov 21, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/subscription-manager-track-renewals/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/subscription-manager-track-renewals
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/subscription-manager-track-renewals.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/subscription-manager-track-renewals)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.

subscription-manager-track-renewals MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the subscription-manager-track-renewals MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 13 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the subscription-manager-track-renewals MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: schedule_delete.

Can the subscription-manager-track-renewals MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the subscription-manager-track-renewals MCP server have?

14 tools: 1 destructive, 12 write, 1 read. schedule_delete, schedule_create, schedule_list, schedule_get, schedule_update, schedule_pause, schedule_resume, schedule_skip and 6 more.

Does the subscription-manager-track-renewals MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the subscription-manager-track-renewals MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the subscription-manager-track-renewals MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.