Subscriptions is answering right now. Last checked 13 min ago. It exposes 14 tools. Last commit 22 Oct 2026.
Recurring subscriptions billing: schedule once, auto-generate due invoice PDFs.
Uptime history
32 days of history · worst day 92%
32 days agonow
100.0%
Uptime 24h
88 of 88 checks
14
Tools
read from the server
186 ms
Response time
average over 24h
2
Stars
last commit 22 Oct 2026
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.
15 Oct
a tool changed version
Nothing serious here today
Today is the operative word: we check Subscriptions every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
run in your terminal
claude mcp add subscriptions --transport http https://mcp.zovo.one/mcp/subscriptionsSettings → Connectors → Add custom connector, then paste this address
https://mcp.zovo.one/mcp/subscriptions~/.codex/config.toml
[mcp_servers.subscriptions]
url = "https://mcp.zovo.one/mcp/subscriptions".cursor/mcp.json
{
"mcpServers": {
"subscriptions": {
"url": "https://mcp.zovo.one/mcp/subscriptions"
}
}
}.vscode/mcp.json
{
"servers": {
"subscriptions": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/subscriptions"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
schedule
schedule_create
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.
schedule_delete
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.
schedule_get
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.
schedule_history
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.
schedule_list
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.
schedule_pause
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.
schedule_resume
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.
schedule_skip
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.
schedule_upcoming
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.
schedule_update
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.
license
license_activate
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.
license_status
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.
forecast
forecast
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.
invoice
invoice_generate_due
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zovo.one/mcp/subscriptions | streamable-http | answering | 127 ms | 13 min ago |
Alternatives to Subscriptions
same job, measured the same wayRecurring Invoice Scheduler Subscription Billing Due Reminders
by theluckystrike
Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue.
Recurring
by theluckystrike
Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue.
MCP Vindi
by codespar
MCP server for Vindi — recurring billing, subscriptions, invoices
Stripe Billing
by theluckystrike
Read your Stripe billing data from AI chat: balances, invoices, subscriptions. Read-only.
Dynt
by dynt-api
Company finances for agents: transactions, invoices, bills, expenses, subscriptions, receipts.
MCP Stripe
by infoinlet-marketplace
Read-only Stripe for AI agents — customers, charges, subscriptions, invoices, balance.
Pdfapi MCP Server
by amranswill
Generate invoice, receipt, and report PDFs from structured JSON via a single API call.
Recurly MCP by usefulapi
by usefulapi
MCP server for Recurly — accounts, subscriptions, invoices, plans; cancel & pause subs.
Subscriptions — questions
Answers built from our own checks of this server.
What can Subscriptions do?
It exposes 14 tools, read directly from the server on our last check. Among them: forecast, invoice_generate_due, license_activate, license_status, schedule_create, schedule_delete and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Subscriptions mostly used for?
Its tools cluster around schedule and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Subscriptions working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 88 checks got a reply (100.0%), average response time 186 ms. The bar chart above shows every period we have measured.
How do I connect Subscriptions?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Subscriptions need an API key?
No. Subscriptions completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Subscriptions?
It answers our handshake in 186 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Subscriptions open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.