Remote MCP · Endpoint

Familia MCP server

No. Familia answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.family.asynq.org/mcp

The last check completed an MCP handshake.

Registry name
com.familiaplanner/familia
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Private family planner for schedules, tasks, checklists, attachments, and availability.
Listing
From the official MCP registry (active).
Recent checks of Familia
CheckedResultHandshake
1 hour agoHandshake completed132 ms
2 days agoHandshake completed139 ms
4 days agoHandshake completed171 ms
5 days agoHandshake completed153 ms
7 days agoHandshake completed121 ms
8 days agoHandshake completed294 ms
9 days agoHandshake completed265 ms
12 days agoHandshake completed196 ms
13 days agoHandshake completed397 ms
15 days agoHandshake completed168 ms
16 days agoHandshake completed149 ms
17 days agoHandshake completed110 ms
18 days agoHandshake completed115 ms
19 days agoHandshake completed52 ms
20 days agoHandshake completed147 ms
21 days agoHandshake completed151 ms
22 days agoHandshake completed116 ms

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

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