Remote MCP · Endpoint

Sunvane Golden Hour MCP server

No. Sunvane Golden Hour answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://golden-hour.zovo.one/mcp

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/golden-hour
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
464 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Sun times & shoot planning
Listing
From the official MCP registry (active).
Recent checks of Sunvane Golden Hour
CheckedResultHandshake
56 minutes agoHandshake completed464 ms
3 days agoHandshake completed99 ms
12 days agoHandshake completed303 ms
13 days agoHandshake completed397 ms
14 days agoHandshake completed585 ms
15 days agoHandshake completed244 ms
17 days agoHandshake completed304 ms
18 days agoHandshake completed1.14 s
18 days agoHandshake completed276 ms
20 days agoHandshake completed497 ms
22 days agoHandshake completed215 ms
25 days agoHandshake completed573 ms
27 days agoHandshake completed223 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 Sunvane Golden Hour and makes no claim about it beyond what these checks measured.