Remote MCP · Endpoint

Heimster – Swiss homes MCP server

No. Heimster – Swiss homes answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://heimster.ch/mcp/public

The last check completed an MCP handshake.

Registry name
ch.heimster/heimster
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
310 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Swiss homes to rent or buy, with walking distances, noise, sun and commute times for any address.
Listing
From the official MCP registry (active).
Recent checks of Heimster – Swiss homes
CheckedResultHandshake
1 hour agoHandshake completed310 ms
1 day agoHandshake completed328 ms
2 days agoHandshake completed319 ms
3 days agoHandshake completed323 ms
3 days agoHandshake completed327 ms
5 days agoHandshake completed321 ms
7 days agoHandshake completed314 ms
10 days agoHandshake completed384 ms
12 days agoHandshake completed426 ms
14 days agoHandshake completed378 ms
16 days agoHandshake completed317 ms
19 days agoHandshake completed367 ms
21 days agoHandshake completed313 ms
23 days agoHandshake completed379 ms
24 days agoHandshake completed321 ms

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

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