Remote MCP · Endpoint

GrowingUpVideo MCP server

No. GrowingUpVideo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://growingupvideo.com/mcp

The last check completed an MCP handshake.

Registry name
com.growingupvideo/growingupvideo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
215 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Turn photos of a person, couple, or pet across the years into an AI growing-up morph video.
Listing
From the official MCP registry (active).
Recent checks of GrowingUpVideo
CheckedResultHandshake
1 hour agoHandshake completed215 ms
9 days agoHandshake completed259 ms
9 days agoHandshake completed211 ms
11 days agoHandshake completed231 ms
12 days agoHandshake completed268 ms
13 days agoHandshake completed217 ms
14 days agoHandshake completed602 ms
14 days agoHandshake completed298 ms
16 days agoHandshake completed440 ms
19 days agoHandshake completed189 ms
21 days agoHandshake completed542 ms
24 days agoHandshake completed605 ms
26 days agoHandshake completed340 ms
28 days agoHandshake completed262 ms

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

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