Remote MCP · Endpoint

Bydleno MCP server

No. Bydleno answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bydleno.cz/api/mcp/

The last check completed an MCP handshake.

Registry name
cz.bydleno/pronajmy
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
450 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search Czech rental listings from 25 portals, merged into one offer per flat.
Listing
From the official MCP registry (active).
Recent checks of Bydleno
CheckedResultHandshake
1 hour agoHandshake completed450 ms
2 days agoHandshake completed476 ms
4 days agoHandshake completed689 ms
5 days agoHandshake completed292 ms
7 days agoHandshake completed301 ms
8 days agoHandshake completed292 ms
9 days agoHandshake completed294 ms
12 days agoHandshake completed295 ms
13 days agoHandshake completed291 ms
15 days agoHandshake completed477 ms
16 days agoHandshake completed302 ms
18 days agoHandshake completed297 ms
19 days agoHandshake completed298 ms
20 days agoHandshake completed614 ms
20 days agoHandshake completed291 ms
21 days agoHandshake completed291 ms
22 days agoHandshake completed479 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 Bydleno and makes no claim about it beyond what these checks measured.