Remote MCP · Endpoint

ServeReel MCP server

No. ServeReel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.servereel.com/mcp

The last check completed an MCP handshake.

Registry name
com.servereel/servereel-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
204 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free 7 day content plans built from a business website. ServeReel creates reels, videos, and images.
Listing
From the official MCP registry (active).
Recent checks of ServeReel
CheckedResultHandshake
1 hour agoHandshake completed204 ms
9 days agoHandshake completed830 ms
10 days agoHandshake completed226 ms
11 days agoHandshake completed192 ms
12 days agoHandshake completed133 ms
14 days agoHandshake completed152 ms
14 days agoHandshake completed138 ms
15 days agoHandshake completed186 ms
17 days agoHandshake completed222 ms
19 days agoHandshake completed169 ms
21 days agoHandshake completed160 ms
24 days agoHandshake completed225 ms
26 days agoHandshake completed178 ms
28 days agoHandshake completed192 ms

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

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