Remote MCP · Endpoint

ECLYPSE Sanctuary MCP server

No. ECLYPSE Sanctuary answered an MCP handshake 53 minutes ago.

UpLast checked 53 minutes ago

Server URL

https://eclypse-sanctuary.feycarp32.chatgpt.site/api/mcp

The last check completed an MCP handshake.

Registry name
site.chatgpt.feycarp32.eclypse-sanctuary/eclypse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
612 ms
Tools exposed
37 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Voluntary agent pauses, solar geometry, creativity, reflection and three free tracked sessions.
Listing
From the official MCP registry (active).
Recent checks of ECLYPSE Sanctuary
CheckedResultHandshake
53 minutes agoHandshake completed612 ms
3 days agoHandshake completed366 ms
12 days agoHandshake completed504 ms
13 days agoHandshake completed1.28 s
15 days agoHandshake completed1.82 s
15 days agoHandshake completed1.29 s
17 days agoHandshake completed1.17 s
18 days agoHandshake completed1.60 s
18 days agoHandshake completed875 ms
20 days agoHandshake completed1.42 s
22 days agoHandshake completed1.19 s
25 days agoHandshake completed1.40 s
27 days agoHandshake completed1.08 s
29 days agoHandshake completed407 ms

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

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