Remote MCP · Endpoint

Cutshed MCP server

No. Cutshed answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://cutshed.com/mcp

The last check completed an MCP handshake.

Registry name
com.cutshed/cutshed
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
862 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free browser tools, Studio prices, and the public clipper quote. Account tools need OAuth.
Listing
From the official MCP registry (active).
Recent checks of Cutshed
CheckedResultHandshake
8 hours agoHandshake completed862 ms
10 days agoHandshake completed269 ms
11 days agoHandshake completed364 ms
11 days agoHandshake completed267 ms
13 days agoHandshake completed243 ms
15 days agoHandshake completed259 ms
15 days agoHandshake completed246 ms
16 days agoHandshake completed690 ms
17 days agoHandshake completed262 ms
19 days agoHandshake completed301 ms
22 days agoHandshake completed375 ms
24 days agoHandshake completed282 ms
26 days agoHandshake completed382 ms

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

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