World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Track subscriptions and renewals from your AI chat: schedules, due dates, reminders, local data.
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 0/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 12/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 8/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 20/100 |
品質: 基本チェック 5/5 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
Subscription Manager Track Renewals をインストールして。https://mcp.popnx.com/i/theluckystrike-subscription-manager-track-renewals.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る
チェック 5/5 合格 · 質問内容は提供元のサーバー(mcp.zovo.one)を通ります · ✓ コマンド確認済み 2026年11月13日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 5 分
Subscription Manager Track Renewals のキーが必要です(提供元のサイトで作成) · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
Subscription Manager Track Renewalshttps://mcp.zovo.one/mcp/subscription-manager-track-renewalsRequest headers に、この名前と値を追加
AuthorizationBearer <ここにキーを貼り付け>キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Claude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsSubscription Manager Track Renewals
Subscription Manager Track Renewals を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Subscription Manager Track Renewals を使っていると言うか、回答に Subscription Manager Track Renewals のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT はまだ Subscription Manager Track Renewals につなげません
Subscription Manager Track Renewals は接続時に自分のキーが必要ですが、OpenAI のヘルプページは OAuth ログインしか説明しておらず、確認できたキー入力方法がありません
A · Subscription Manager Track Renewals につなげるアプリを使う
B · その他 の中で ChatGPT につなげる別のサーバー
同じカテゴリでよく使われているものから、キーなしでアドレスだけでつなげるものを選びました
Claude Code につなげます · 約 5 分
Subscription Manager Track Renewals のキーが必要です(提供元のサイトで作成)
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user subscription-manager-track-renewals https://mcp.zovo.one/mcp/subscription-manager-track-renewals --header 'Authorization: Bearer your-value'Enter の前に「your-value」を自分のキーに書き換えてください
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Subscription Manager Track Renewals が一覧にあり、接続済みと表示されれば OK です
Subscription Manager Track Renewals を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が Subscription Manager Track Renewals を使っていると言うか、回答に Subscription Manager Track Renewals のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 5 分
Subscription Manager Track Renewals のキーが必要です(提供元のサイトで作成)
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
Subscription Manager Track Renewals の設定で Authorization が空です。自分のキーを入れて保存します
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Subscription Manager Track Renewals を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が Subscription Manager Track Renewals を使っていると言うか、回答に Subscription Manager Track Renewals のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 5 分
Subscription Manager Track Renewals のキーが必要です(提供元のサイトで作成)
提供元のサイトで登録し、次の手順で使う API キーを作ります。料金や無料プランは提供元のサイトで確認してください。
Subscription Manager Track Renewals の設定で Authorization が空です。自分のキーを入れて保存します
キーはアプリの入力欄にだけ貼り付け、チャットに貼ったり人に送ったりしないでください
Subscription Manager Track Renewals を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Subscription Manager Track Renewals を使っていると言うか、回答に Subscription Manager Track Renewals のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code
claude mcp add --transport http --scope user subscription-manager-track-renewals https://mcp.zovo.one/mcp/subscription-manager-track-renewals --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"subscription-manager-track-renewals": {
"url": "https://mcp.zovo.one/mcp/subscription-manager-track-renewals",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"subscription-manager-track-renewals": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/subscription-manager-track-renewals",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}説明は英語の原文のままです。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
ツールの名前と説明は、サーバーが2026年11月14日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
schedule_createDefine 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.
schedule_listList 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.
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. schedule_history is the log.
schedule_updateChange 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.
schedule_pauseStop 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.
schedule_resumeMake 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.
schedule_deleteDelete 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.
schedule_skipClose 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.
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. Free lists the first 3 in your horizon.
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. Returns what was created, what was skipped and what is still due.
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. schedule_list finds the id. Pro.
forecastExpected 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.
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. Call it to explain a free-tier refusal. No arguments, nothing changes.
license_activateTurn Pro on for this connection with key, an MCPL1. . 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.
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月18日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント theluckystrike で確認済みです
コードの最終更新:今日
MITを使用
578ミリ秒で応答(HTTP 200)
サインイン不要
14件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/theluckystrike-subscription-manager-track-renewals)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:Authorization
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は今日、最新バージョン(0.23.1)がレジストリに届いたのは2 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| これ Subscription Manager Track Renewals | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 |
| キーが必要 | はい | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| 基本チェック | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| ライセンス | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Say "bill Acme 12 hours at 90 EUR on the 1st of every month" once, and stop remembering it. This MCP server stores recurring invoice schedules, client, line items, cadence, start and end dates, and then, when you ask, creates the invoices that have actually fallen due as real records in the invoice server, with its number series, its clients and its A4 PDF. Generation is idempotent: one invoice per schedule per period, keyed by the occurrence date, so running the billing run twice on the same day creates nothing the second time. It also answers "what falls due in the next 30 days" and "what will I invoice per month for the next year". Everything is stored in plain JSON files on your own machine; nothing is uploaded anywhere.
In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Frecurring-invoice-scheduler-subscription-billing-due-reminders/versions/latest) (io.github.theluckystrike/recurring-invoice-scheduler-subscription-billing-due-reminders).
Define a repeating invoice once, generate the due PDFs from chat, no billing SaaS required.
npm publish for @theluckystrike/mcp-recurring is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.
One-click (.mcpb): download recurring.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest
(claude_desktop_config.json):
{
"mcpServers": { "recurring": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-recurring"] } } }
Claude Code:
claude mcp add recurring -- npx -y @theluckystrike/mcp-recurring
(.cursor/mcp.json):
{
"mcpServers": { "recurring": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-recurring"] } } }
The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these three commands:
git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers
npm install npm run build -w packages/mcp-license -w servers/invoice -w servers/recurring
Then point your client's command at node with one arg: the absolute path to servers/recurring/dist/index.js.
To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.
invoice_list, counts in overdue_report and can be re-rendered with invoice_pdf. Set your issuer details once with business_set there; this server has no business_set of its own on purpose, so there is only one profile to keep right.| Tool | What it does |
|---|---|
schedule_create | Define a repeating invoice: client, items, cadence, start date, optional end date, due days, notes |
schedule_list | Every schedule with cadence, amount per period, next due date and status |
schedule_get | Full record for one schedule, plus how many invoices it has generated |
schedule_update | Change client, items, currency, cadence, dates, due days or notes. Periods already invoiced are never re-issued |
schedule_pause | Stop generating without deleting; history is kept |
schedule_resume | Make it active again. Periods that fell due while paused are still due |
schedule_delete | Remove the schedule. Invoices it made stay in the invoice server and its history is kept as an audit trail. A re-created schedule gets a new id, so invoice_generate_due warns when it re-covers a period the old one already billed |
schedule_skip | Skip ONE occurrence for good, without pausing the schedule -- the answer to "do not bill this client for October". undo: true puts the period back |
schedule_upcoming | What falls due in the next N days, with amounts and totals per currency, plus any period that already fell due and was never invoiced. Free covers 30 days |
invoice_generate_due | Create the invoices that are due as of a date and render their PDFs. Idempotent, keyed by period; reports created and skipped. At most 60 invoices per call, oldest period first, and it says how many are still due. dry_run shows the run first. Free and unlimited |
schedule_history | Pro: the audit log for one schedule -- every period, invoice number, dates, amount, paid status and PDF path |
forecast | Expected revenue per calendar month per currency, with paused schedules listed separately rather than dropped. Free covers 3 months |
license_status | Show free or Pro mode |
license_activate | Activate a Pro key (verified offline) |
Resource: recurring://upcoming returns the next 30 days of occurrences as JSON. Prompt: monthly_billing_run, dry run, generate, list what is coming, then report who needs a payment reminder.
| You say | Tool |
|---|---|
| "Bill Acme 12 hours at 90 EUR every month from the 1st." | schedule_create |
| "What recurring invoices do I have?" | schedule_list |
| "What is due in the next 30 days?" | schedule_upcoming |
| "Run this month's billing." | monthly_billing_run / invoice_generate_due |
| "Show me what would be created before you create it." | invoice_generate_due {dry_run: true} |
| "Pause the Beta Corp retainer, they are on hold." | schedule_pause |
| "Do not bill Acme for October." | schedule_skip |
| "Put the Acme retainer up to 100 EUR an hour from now on." | schedule_update |
| "How much will I invoice per month next year?" | forecast |
| "Show me every invoice this retainer has produced." | schedule_history |
You: Bill Acme 12 hours at 90 EUR a month, starting 1 June, 14 day terms.
schedule_create { client: "Acme Retainer", currency: "EUR", every: "monthly", start_date: "2026-06-01", due_days: 14, items: [{ description: "Retainer hours", quantity: 12, unit_price: 90 }] } -> schedule 9f2c1a04, next dates 2026-06-01, 2026-07-01, 2026-08-01, 2026-09-01
You (on 3 September): Run the billing.
invoice_generate_due {} -> as_of 2026-09-03: created 4 invoices, skipped 0 already invoiced. INV-2026-0001 Acme Retainer period 2026-06-01 EUR 1080.00 due 2026-06-15 .../pdf/INV-2026-0001.pdf INV-2026-0002 Acme Retainer period 2026-07-01 EUR 1080.00 due 2026-07-15 .../pdf/INV-2026-0002.pdf INV-2026-0003 Acme Retainer period 2026-08-01 EUR 1080.00 due 2026-08-15 .../pdf/INV-2026-0003.pdf INV-2026-0004 Acme Retainer period 2026-09-01 EUR 1080.00 due 2026-09-15 .../pdf/INV-2026-0004.pdf Total: EUR 4320.00
You (five minutes later, having forgotten): Run the billing.
invoice_generate_due {} -> as_of 2026-09-03: created 0 invoices, skipped 4 already invoiced.
The second run is the point: the period, not the calendar day, is the key, so a repeated billing run is a no-op rather than a duplicate invoice sitting in a client's inbox.
| Free | Pro | |
|---|---|---|
| Active schedules | 3 | Unlimited |
invoice_generate_due | Yes, unlimited | Yes, unlimited |
schedule_upcoming horizon | 30 days | Up to 10 years |
forecast | 3 months | Up to 120 months |
schedule_history audit log | No | Yes |
End-of-month and anchor-day rules (anchor_day, end_of_month) | No, bills on the start date's day of month | Yes |
| Pause, resume, update, delete, dry run, multi-currency | Yes | Yes |
Pro is a one-time $19, or $39 for every server in the collection, lifetime.
Every date is a local ISO calendar date, YYYY-MM-DD. An occurrence is the k-th step from start_date, and occurrence 0 is start_date itself, so a schedule starting today is due today.
weekly = +7 days per step. {days: n} = +n days per step.monthly = +1 month, quarterly = +3 months, yearly = +12 months.start_date and clamps it to the length of the target month; it never carries the clamp forward. From 2026-01-31 the series is 01-31, 02-28, 03-31, 04-30, 05-31, February does not silently turn a month-end retainer into a 28th-of-the-month retainer.2028-02-29 fall on 02-28 in common years and back on 02-29 in the next leap year.anchor_day replaces the day of month before clamping, so anchor_day: 31 means the last day of every month; end_of_month: true does the same explicitly. Both are ignored for weekly and {days: n}, which have no month to anchor to. An anchored first occurrence that would land before start_date is dropped, never billed early.end_date is generated; the next one is not.start_date: it jumps to an estimate near the date you asked about and scans forward from there, so a daily schedule created in 2010 still reports what is due in 2026 instead of exhausting its per-run occurrence cap walking there one day at a time.Amounts are held as integer minor units by the invoice engine, the same ISO 4217 table, the same round-per-line-then-sum contract, so a schedule's amount and the invoice it produces can never disagree. Each line's gross is rounded first, tax is computed and rounded per line and grouped into one line per rate, and the totals are integer sums of those already-rounded values. A schedule bills in its own currency, or your business default currency if it has none; nothing here converts between currencies.
Schedules and the generation log live in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/recurring/ as schedules.json and history.json. The go into the invoice server's directory, ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/invoice/, with their PDFs under its pdf/ subfolder, the same files invoice_list, overdue_report and invoice_pdf read there.
Every mutation runs under an advisory lock file. Anything that writes an invoice takes two locks, always in the same order, recurring/.lock first, then invoice/.lock, so two billing runs (or a billing run and a hand-written invoice in the other server) cannot interleave, cannot allocate the same invoice number and cannot deadlock. Invoice numbers are allocated inside the lock; the PDFs are rendered after it is released, so a slow render never holds up the counter. Saves go to a temporary file and are renamed into place.
If schedules.json or history.json is unreadable or not valid JSON it is never treated as "empty": the file is moved aside byte-for-byte as .json.corrupt- , a .json.corrupt marker is written, and every tool fails loudly until you restore a good copy and delete the marker. This matters more here than anywhere else in the collection: a history.json silently read as empty would re-bill every period the schedule has ever covered.