Remote MCP · Endpoint

LovedOne Family MCP MCP server

No. LovedOne Family MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.lovedone.app/mcp/v1

The last check completed an MCP handshake.

Registry name
app.lovedone/family-inbox
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
106 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Authenticated MCP for one family household: loved ones, members, and Family Inbox plaintext.
Listing
From the official MCP registry (active).
Recent checks of LovedOne Family MCP
CheckedResultHandshake
1 hour agoHandshake completed106 ms
23 hours agoHandshake completed153 ms
2 days agoHandshake completed105 ms
4 days agoCredentials required—
6 days agoCredentials required—
9 days agoCredentials required—
11 days agoCredentials required—
13 days agoCredentials required—
15 days agoCredentials required—
17 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
23 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 LovedOne Family MCP and makes no claim about it beyond what these checks measured.