Remote MCP · Endpoint

AnimateMyTravel Studio MCP server

No. AnimateMyTravel Studio answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.animatemytravel.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.animatemytravel/studio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Animated map videos of any story: trips, wars, empires, storms, data. Free, no signup.
Listing
From the official MCP registry (active).
Recent checks of AnimateMyTravel Studio
CheckedResultHandshake
1 hour agoHandshake completed383 ms
2 days agoHandshake completed418 ms
4 days agoHandshake completed414 ms
7 days agoHandshake completed381 ms
9 days agoHandshake completed382 ms
11 days agoHandshake completed203 ms
13 days agoHandshake completed385 ms
15 days agoHandshake completed310 ms
17 days agoHandshake completed383 ms
19 days agoHandshake completed353 ms
20 days agoHandshake completed384 ms
22 days agoHandshake completed424 ms
23 days agoHandshake completed471 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 AnimateMyTravel Studio and makes no claim about it beyond what these checks measured.