Remote MCP · Endpoint

Tomorrow Lives Engines MCP server

No. Tomorrow Lives Engines answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tomorrowlives.com/api/agents/mcp

The last check completed an MCP handshake.

Registry name
com.tomorrowlives/engines
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
360 ms
Tools exposed
57 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Reproducible, IP-clean assets for agents: seven engines, from print designs to voice and video.
Listing
From the official MCP registry (active).
Recent checks of Tomorrow Lives Engines
CheckedResultHandshake
1 hour agoHandshake completed360 ms
1 day agoHandshake completed300 ms
2 days agoHandshake completed286 ms
2 days agoHandshake completed297 ms
4 days agoHandshake completed336 ms
7 days agoHandshake completed273 ms
9 days agoHandshake completed273 ms
12 days agoHandshake completed276 ms
14 days agoHandshake completed382 ms
16 days agoHandshake completed312 ms
18 days agoHandshake completed428 ms
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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

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