Remote MCP · Endpoint

Cancel My Sub MCP server

No. Cancel My Sub answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://goodturn-mcp.pages.dev/cancelmysub/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/cancelmysub
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
How to cancel US and UK subscriptions, the last safe day to cancel, and what a card charge is.
Listing
From the official MCP registry (active).
Recent checks of Cancel My Sub
CheckedResultHandshake
53 minutes agoHandshake completed64 ms
3 days agoHandshake completed79 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed54 ms
15 days agoHandshake completed53 ms
15 days agoHandshake completed48 ms
17 days agoHandshake completed61 ms
18 days agoHandshake completed49 ms
18 days agoHandshake completed47 ms
20 days agoHandshake completed66 ms
22 days agoHandshake completed82 ms
25 days agoHandshake completed48 ms
27 days agoHandshake completed94 ms
29 days agoHandshake completed62 ms

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

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