Remote MCP · Endpoint

Daydream MCP server

No. Daydream answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://gen.daydream.live/mcp

The last check completed an MCP handshake.

Registry name
live.daydream.gen/music
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Original instrumental songs from words, each with five stems. Royalty-free, for games and videos.
Listing
From the official MCP registry (active).
Recent checks of Daydream
CheckedResultHandshake
3 hours agoHandshake completed216 ms
3 days agoHandshake completed73 ms
13 days agoHandshake completed354 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed111 ms
16 days agoHandshake completed91 ms
18 days agoHandshake completed133 ms
18 days agoHandshake completed78 ms
19 days agoHandshake completed62 ms
21 days agoHandshake completed194 ms
22 days agoHandshake completed88 ms
25 days agoHandshake completed71 ms
27 days agoHandshake completed87 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 Daydream and makes no claim about it beyond what these checks measured.