Remote MCP · Endpoint

Framezone MCP server

No. Framezone answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://framezone.app/mcp

The last check completed an MCP handshake.

Registry name
app.framezone/framezone
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.03 s
Tools exposed
50 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Your life dashboard for AI: tasks, habits, goals, budgets, workouts, nutrition, journal, notes.
Listing
From the official MCP registry (active).
Recent checks of Framezone
CheckedResultHandshake
52 minutes agoHandshake completed1.03 s
2 days agoHandshake completed216 ms
4 days agoHandshake completed224 ms
5 days agoHandshake completed219 ms
7 days agoHandshake completed163 ms
8 days agoHandshake completed266 ms
9 days agoHandshake completed856 ms
12 days agoHandshake completed188 ms
13 days agoHandshake completed206 ms
15 days agoHandshake completed165 ms
17 days agoHandshake completed177 ms
18 days agoHandshake completed171 ms
19 days agoHandshake completed173 ms
20 days agoHandshake completed191 ms
21 days agoHandshake completed207 ms
21 days agoHandshake completed295 ms

The last 16 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 Framezone and makes no claim about it beyond what these checks measured.