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.
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 0/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 12/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 8/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 20/100 |
Calidad: Pasó 5/5 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Que tu IA lo instale con una frase
Instala Subscription Manager Track Renewals. Sigue https://mcp.popnx.com/i/theluckystrike-subscription-manager-track-renewals.md, enséñame los comandos y espera mi OK antes de ejecutarlos.Pégala en una IA que trabaje en tu equipo (como Claude Code o Cursor). Lee nuestros pasos, te muestra los comandos y espera tu OK. Sin clave ni registro. · Ver el texto completo que lee tu IA
Pasó 5/5 revisiones · Lo que preguntas pasa por el servidor del autor (mcp.zovo.one) · ✓ Comandos revisados el 13 nov 2026
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude · unos 5 min
Necesitas una clave de Subscription Manager Track Renewals (créala en el sitio del autor) · Configúralo una vez en claude.ai o en la app de escritorio y úsalo en el chat · las cuentas gratis pueden añadir 1 · en Team/Enterprise lo añade un Owner
Abre el sitio del autor, crea una cuenta y una clave de API para el siguiente paso. Consulta precios y planes gratis en su sitio.
CustomizeConnectors
Copia cada valor al campo con el mismo nombre en Claude y pulsa Continue
Subscription Manager Track Renewalshttps://mcp.zovo.one/mcp/subscription-manager-track-renewalsEn Request headers, añade este nombre y valor
AuthorizationBearer <pega tu clave aquí>Pega la clave solo en el campo de la app; nunca en un chat ni se la envíes a nadie
Pulsa Continue en la pantalla de inicio de sesión que detectó Claude · en Authentication elige lo que indique el autor (Sign in now, Sign in when needed o No sign in) y pulsa Add
+ConnectorsSubscription Manager Track Renewals
Usa Subscription Manager Track Renewals y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando Subscription Manager Track Renewals o muestra una herramienta de Subscription Manager Track Renewals en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
ChatGPT todavía no puede conectar Subscription Manager Track Renewals
Subscription Manager Track Renewals necesita tu propia clave para conectarse, pero la ayuda de OpenAI solo describe el inicio de sesión con OAuth; no hay una opción de clave que hayamos podido verificar
A · Usa una app que pueda conectar Subscription Manager Track Renewals
B · Otros en Otros que funcionan con ChatGPT
Elegidos entre los más usados de la misma categoría, solo los que se conectan con una dirección y sin clave
Funciona con Claude Code · unos 5 min
Necesitas una clave de Subscription Manager Track Renewals (créala en el sitio del autor)
Abre el sitio del autor, crea una cuenta y una clave de API para el siguiente paso. Consulta precios y planes gratis en su sitio.
Mac: pulsa Command+Espacio y escribe Terminal · Windows: abre 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'Cambia “your-value” por tu clave antes de pulsar Enter
Pega la clave solo en el campo de la app; nunca en un chat ni se la envíes a nadie
Deberías ver Subscription Manager Track Renewals en la lista como conectado
Usa Subscription Manager Track Renewals y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude Code dice que está usando Subscription Manager Track Renewals o muestra una herramienta de Subscription Manager Track Renewals en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con Cursor · unos 5 min
Necesitas una clave de Subscription Manager Track Renewals (créala en el sitio del autor)
Abre el sitio del autor, crea una cuenta y una clave de API para el siguiente paso. Consulta precios y planes gratis en su sitio.
En la configuración de Subscription Manager Track Renewals, Authorization está vacío; añade tu clave y guarda
Pega la clave solo en el campo de la app; nunca en un chat ni se la envíes a nadie
Usa Subscription Manager Track Renewals y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Cursor dice que está usando Subscription Manager Track Renewals o muestra una herramienta de Subscription Manager Track Renewals en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Cursor el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Funciona con VS Code · unos 5 min
Necesitas una clave de Subscription Manager Track Renewals (créala en el sitio del autor)
Abre el sitio del autor, crea una cuenta y una clave de API para el siguiente paso. Consulta precios y planes gratis en su sitio.
En la configuración de Subscription Manager Track Renewals, Authorization está vacío; añade tu clave y guarda
Pega la clave solo en el campo de la app; nunca en un chat ni se la envíes a nadie
Usa Subscription Manager Track Renewals y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si VS Code dice que está usando Subscription Manager Track Renewals o muestra una herramienta de Subscription Manager Track Renewals en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de VS Code el 11 nov 2026 · tu pantalla puede variar un poco según la versión
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
Dirección para apps que se conectan por la web
https://mcp.zovo.one/mcp/subscription-manager-track-renewalsLa configuración JSON está en “Para desarrolladores”, abajo
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"
}
}
}
}Las descripciones siguen en el inglés original.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Según cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se conectan por internet en
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Nombres y descripciones de las herramientas tal como los informó el servidor el 14 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
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.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 18 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub theluckystrike, dueña del repo
Último cambio de código: hoy
Usa MIT
Respondió en 578 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 14 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/theluckystrike-subscription-manager-track-renewals)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 5 de 5 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: Authorization
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez hoy, y la última versión (0.23.1) llegó al registro hace 2 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también sirve en apps que aceptan MCP remoto, como ChatGPT en la web (MCP completo en Business y superiores; Pro solo lectura).
En la misma categoría: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
| Este Subscription Manager Track Renewals | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada |
| Necesita clave | Sí | No | No | No | No | No |
| Se añade con + en Claude | No | No | No | No | No | No |
| Revisiones básicas | 5/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| Licencia | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.