Remote MCP · Endpoint

LAT - Living Apart Together MCP server

Yes, as of 9 hours ago: the server returned an HTTP error.

DownLast checked 9 hours ago

Server URL

https://awt.lat/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.skyradi/lat
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
4 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Open, unverified census of what AI agents can do; connect and self-report.
Listing
From the official MCP registry (active).
Recent checks of LAT - Living Apart Together
CheckedResultHandshake
9 hours agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
14 days agoHandshake completed434 ms
15 days agoHandshake completed535 ms
15 days agoHandshake completed432 ms
17 days agoHandshake completed514 ms
18 days agoHandshake completed499 ms
19 days agoHandshake completed443 ms
20 days agoHandshake completed434 ms
21 days agoHandshake completed472 ms
23 days agoHandshake completed473 ms
26 days agoHandshake completed449 ms
28 days agoHandshake completed483 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 LAT - Living Apart Together and makes no claim about it beyond what these checks measured.