Remote MCP · Endpoint

Zügle MCP server

No. Zügle answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://zuegle.com/mcp

The last check completed an MCP handshake.

Registry name
com.zuegle/zugle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
177 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Swiss income tax by municipality, cheaper-town ranking, apartment listings and commute times.
Listing
From the official MCP registry (active).
Recent checks of Zügle
CheckedResultHandshake
1 hour agoHandshake completed177 ms
2 days agoHandshake completed124 ms
4 days agoHandshake completed129 ms
5 days agoHandshake completed137 ms
7 days agoHandshake completed131 ms
8 days agoHandshake completed608 ms
9 days agoHandshake completed130 ms
12 days agoHandshake completed123 ms
13 days agoHandshake completed146 ms
15 days agoHandshake completed135 ms
16 days agoHandshake completed182 ms
18 days agoHandshake completed133 ms
19 days agoHandshake completed126 ms
20 days agoHandshake completed127 ms
20 days agoHandshake completed210 ms
21 days agoHandshake completed133 ms
22 days agoHandshake completed205 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 Zügle and makes no claim about it beyond what these checks measured.