Remote MCP · Endpoint

TubeChop MCP server

No. TubeChop answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tubechop.com/mcp

The last check completed an MCP handshake.

Registry name
com.tubechop/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create shareable clips from public YouTube videos using exact start and end times.
Listing
From the official MCP registry (active).
Recent checks of TubeChop
CheckedResultHandshake
1 hour agoHandshake completed128 ms
2 days agoHandshake completed59 ms
4 days agoHandshake completed53 ms
5 days agoHandshake completed84 ms
7 days agoHandshake completed109 ms
8 days agoHandshake completed379 ms
9 days agoHandshake completed66 ms
12 days agoHandshake completed51 ms
13 days agoHandshake completed99 ms
15 days agoHandshake completed63 ms
16 days agoHandshake completed89 ms
18 days agoHandshake completed52 ms
19 days agoHandshake completed55 ms
20 days agoHandshake completed78 ms
20 days agoHandshake completed54 ms
21 days agoHandshake completed69 ms
22 days agoHandshake completed139 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 TubeChop and makes no claim about it beyond what these checks measured.