Remote MCP · Endpoint

Squish MCP server

No. Squish answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.getsquish.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.getsquish/squish
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
721 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Give AI random access to video: timestamped contact sheets + zoom into any start/end range.
Listing
From the official MCP registry (active).
Recent checks of Squish
CheckedResultHandshake
2 hours agoHandshake completed721 ms
2 days agoHandshake completed712 ms
4 days agoHandshake completed912 ms
5 days agoHandshake completed714 ms
7 days agoHandshake completed735 ms
8 days agoHandshake completed701 ms
9 days agoHandshake completed700 ms
12 days agoHandshake completed703 ms
13 days agoHandshake completed699 ms
15 days agoHandshake completed717 ms
17 days agoHandshake completed700 ms
18 days agoHandshake completed690 ms
19 days agoHandshake completed754 ms
20 days agoHandshake completed698 ms
20 days agoHandshake completed712 ms
21 days agoHandshake completed721 ms
22 days agoHandshake completed702 ms

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

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