Remote MCP · Endpoint

bissl - menus in Austria MCP server

No. bissl - menus in Austria answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://api.bissl.at/mcp

The last check completed an MCP handshake.

Registry name
at.bissl/bissl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
302 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Dishes, prices, diets, allergens and this week's lunch menus of places to eat in Austria.
Listing
From the official MCP registry (active).
Recent checks of bissl - menus in Austria
CheckedResultHandshake
6 hours agoHandshake completed302 ms
9 days agoHandshake completed306 ms
10 days agoHandshake completed296 ms
11 days agoHandshake completed298 ms
12 days agoHandshake completed307 ms
14 days agoHandshake completed304 ms
15 days agoHandshake completed301 ms
15 days agoHandshake completed345 ms
17 days agoHandshake completed295 ms
19 days agoHandshake completed305 ms
22 days agoHandshake completed515 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed296 ms
28 days agoHandshake completed346 ms

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

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