Remote MCP · Endpoint
io.github.theluckystrike/subscription-manager-track-renewals MCP server
No. io.github.theluckystrike/subscription-manager-track-renewals answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.zovo.one/mcp/subscription-manager-track-renewals
The last check completed an MCP handshake.
- Registry name
- io.github.theluckystrike/subscription-manager-track-renewals
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 63 ms
- Tools exposed
- 14 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Track subscriptions and renewals from your AI chat: schedules, due dates, reminders, local data.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 63 ms |
| 1 day ago | Handshake completed | 73 ms |
| 2 days ago | Handshake completed | 812 ms |
| 3 days ago | Handshake completed | 656 ms |
| 4 days ago | Handshake completed | 615 ms |
| 5 days ago | Handshake completed | 55 ms |
| 6 days ago | Handshake completed | 85 ms |
| 9 days ago | Handshake completed | 1.02 s |
| 11 days ago | Handshake completed | 1.45 s |
| 14 days ago | Handshake completed | 150 ms |
| 16 days ago | Handshake completed | 767 ms |
| 18 days ago | Handshake completed | 716 ms |
| 20 days ago | Handshake completed | 545 ms |
| 22 days ago | Handshake completed | 520 ms |
| 24 days ago | Handshake completed | 159 ms |
| 26 days ago | Handshake completed | 535 ms |
| 27 days ago | Handshake completed | 227 ms |
| 29 days ago | Handshake completed | 418 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 28.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with io.github.theluckystrike/subscription-manager-track-renewals and makes no claim about it beyond what these checks measured.