Remote MCP · Endpoint

io.github.theluckystrike/subscriptions MCP server

No. io.github.theluckystrike/subscriptions answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://mcp.zovo.one/mcp/subscriptions

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/subscriptions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
41 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Recurring subscriptions billing: schedule once, auto-generate due invoice PDFs.
Listing
From the official MCP registry (active).
Recent checks of io.github.theluckystrike/subscriptions
CheckedResultHandshake
52 minutes agoHandshake completed41 ms
3 days agoHandshake completed26 ms
12 days agoHandshake completed29 ms
13 days agoHandshake completed46 ms
15 days agoHandshake completed64 ms
15 days agoHandshake completed43 ms
17 days agoHandshake completed26 ms
18 days agoHandshake completed41 ms
18 days agoHandshake completed740 ms
20 days agoHandshake completed150 ms
22 days agoHandshake completed80 ms
25 days agoHandshake completed23 ms
27 days agoHandshake completed118 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.

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/subscriptions and makes no claim about it beyond what these checks measured.