Remote MCP · Endpoint

Life Scenario MCP server

No. Life Scenario answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lifescenario.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.lifescenario/info
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
319 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
For parents and teachers: SEL trait guides, practice scenarios, what-to-say guides (ages 6-14).
Listing
From the official MCP registry (active).
Recent checks of Life Scenario
CheckedResultHandshake
1 hour agoHandshake completed319 ms
2 days agoHandshake completed334 ms
4 days agoHandshake completed356 ms
7 days agoHandshake completed153 ms
9 days agoHandshake completed72 ms
11 days agoHandshake completed97 ms
13 days agoHandshake completed73 ms
14 days agoHandshake completed57 ms
16 days agoHandshake completed86 ms
18 days agoHandshake completed66 ms
18 days agoHandshake completed66 ms
20 days agoHandshake completed79 ms
22 days agoHandshake completed61 ms
24 days agoHandshake completed163 ms

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