Remote MCP · Endpoint

Magic Hour MCP server

No. Magic Hour answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://mcp.magichour.ai/

The last check completed an MCP handshake.

Registry name
io.github.magichourhq/magic-hour
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create and edit images, videos, and audio through Magic Hour's hosted Streamable HTTP MCP server.
Listing
From the official MCP registry (active).
Recent checks of Magic Hour
CheckedResultHandshake
1 day agoHandshake completed54 ms
3 days agoHandshake completed45 ms
5 days agoHandshake completed64 ms
6 days agoHandshake completed71 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed52 ms
10 days agoHandshake completed55 ms
13 days agoHandshake completed64 ms
14 days agoHandshake completed67 ms
16 days agoHandshake completed79 ms
17 days agoHandshake completed55 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed82 ms
20 days agoHandshake completed50 ms
21 days agoHandshake completed55 ms
22 days agoHandshake completed59 ms
23 days agoHandshake completed54 ms

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

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