Remote MCP · Endpoint

LivinIsto CZ — home watch MCP server

No. LivinIsto CZ — home watch answered an MCP handshake 27 minutes ago.

UpLast checked 27 minutes ago

Server URL

https://www.livinisto.cz/mcp/zamery

The last check completed an MCP handshake.

Registry name
cz.livinisto/intents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Watches Czech home listings for a buyer. Takes no contact; active only after e-mail opt-in.
Listing
From the official MCP registry (active).
Recent checks of LivinIsto CZ — home watch
CheckedResultHandshake
27 minutes agoHandshake completed163 ms
10 days agoHandshake completed158 ms
11 days agoHandshake completed205 ms
12 days agoHandshake completed156 ms
13 days agoHandshake completed167 ms
14 days agoHandshake completed184 ms
15 days agoHandshake completed161 ms
16 days agoHandshake completed277 ms
17 days agoHandshake completed181 ms
19 days agoHandshake completed845 ms
22 days agoHandshake completed135 ms
24 days agoHandshake completed172 ms
26 days agoHandshake completed201 ms

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

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 LivinIsto CZ — home watch and makes no claim about it beyond what these checks measured.