Remote MCP · Endpoint

Stackcut MCP server

No. Stackcut answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://stackcut.io/mcp

The last check completed an MCP handshake.

Registry name
io.stackcut/stackcut
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Cancel or cut any subscription: exit steps, cheaper plans, alternatives and the cheapest stack.
Listing
From the official MCP registry (active).
Recent checks of Stackcut
CheckedResultHandshake
1 hour agoHandshake completed80 ms
2 days agoHandshake completed224 ms
4 days agoHandshake completed71 ms
6 days agoHandshake completed92 ms
7 days agoHandshake completed67 ms
9 days agoHandshake completed117 ms
10 days agoHandshake completed70 ms
11 days agoHandshake completed66 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed63 ms
17 days agoHandshake completed68 ms
18 days agoHandshake completed78 ms
20 days agoHandshake completed68 ms
21 days agoHandshake completed158 ms
22 days agoHandshake completed60 ms

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

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