Remote MCP · Endpoint

Streamloop MCP server

No. Streamloop answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.streamloop.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.streamloop/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
287 ms
Tools exposed
67 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Manage cloud-hosted 24/7 video streams, playlists, destinations, schedules, media and workspaces.
Listing
From the official MCP registry (active).
Recent checks of Streamloop
CheckedResultHandshake
5 hours agoHandshake completed287 ms
10 hours agoHandshake completed272 ms
2 days agoHandshake completed307 ms
4 days agoHandshake completed233 ms
7 days agoHandshake completed230 ms
9 days agoHandshake completed302 ms
11 days agoHandshake completed328 ms
13 days agoHandshake completed316 ms
15 days agoHandshake completed397 ms
18 days agoHandshake completed270 ms
20 days agoHandshake completed474 ms
21 days agoHandshake completed235 ms
23 days agoHandshake completed348 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 Streamloop and makes no claim about it beyond what these checks measured.