Remote MCP · Endpoint

BingeTube MCP server

No. BingeTube answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://binge.tube/mcp

The last check completed an MCP handshake.

Registry name
tube.binge/bingetube
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Search and recommend short drama series on BingeTube (binge.tube), with watch links.
Listing
From the official MCP registry (active).
Recent checks of BingeTube
CheckedResultHandshake
3 hours agoHandshake completed148 ms
4 days agoHandshake completed2.10 s
14 days agoHandshake completed136 ms
15 days agoHandshake completed343 ms
15 days agoHandshake completed149 ms
17 days agoHandshake completed264 ms
18 days agoHandshake completed142 ms
19 days agoHandshake completed157 ms
20 days agoHandshake completed117 ms
21 days agoHandshake completed281 ms
23 days agoHandshake completed137 ms

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

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