Remote MCP · Endpoint

Amtsblick MCP server

No. Amtsblick answered an MCP handshake 22 hours ago.

UpLast checked 22 hours ago

Server URL

https://amtsblick.aicodelabs.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.haraldrohan/amtsblick
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
306 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Wetter und Pegel je Gemeinde in Österreich. Privates Projekt, kein offizielles Behördenangebot.
Listing
From the official MCP registry (active).
Recent checks of Amtsblick
CheckedResultHandshake
22 hours agoHandshake completed306 ms
11 days agoHandshake completed322 ms
11 days agoHandshake completed329 ms
12 days agoHandshake completed345 ms
14 days agoHandshake completed340 ms
15 days agoHandshake completed312 ms
15 days agoHandshake completed314 ms
16 days agoHandshake completed321 ms
18 days agoHandshake completed324 ms
20 days agoHandshake completed323 ms
22 days agoHandshake completed315 ms
25 days agoHandshake completed319 ms
27 days agoHandshake completed323 ms
29 days agoHandshake completed315 ms

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

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