Remote MCP · Endpoint

Dojazdomat MCP server

No. Dojazdomat answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://dojazdomat.sapcorp.eu/mcp

The last check completed an MCP handshake.

Registry name
io.github.MikolajSapek/dojazdomat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.08 s
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Warsaw commute times and rent medians: rank neighborhoods for an office (transit, bike, walk, car).
Listing
From the official MCP registry (active).
Recent checks of Dojazdomat
CheckedResultHandshake
42 minutes agoHandshake completed1.08 s
3 days agoHandshake completed415 ms
12 days agoHandshake completed575 ms
12 days agoHandshake completed444 ms
14 days agoHandshake completed432 ms
15 days agoHandshake completed499 ms
16 days agoHandshake completed404 ms
17 days agoHandshake completed521 ms
18 days agoHandshake completed484 ms
19 days agoHandshake completed427 ms
22 days agoHandshake completed476 ms
25 days agoHandshake completed451 ms
27 days agoHandshake completed971 ms

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

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