Remote MCP · Endpoint

Bolig Tracker MCP server

No. Bolig Tracker answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://bolig-tracker.online/mcp

The last check completed an MCP handshake.

Registry name
online.bolig-tracker/valuations
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
250 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Market-value estimates, comparable sales and property tax for Danish homes, from public registers.
Listing
From the official MCP registry (active).
Recent checks of Bolig Tracker
CheckedResultHandshake
43 minutes agoHandshake completed250 ms
9 days agoHandshake completed186 ms
10 days agoHandshake completed231 ms
11 days agoHandshake completed198 ms
12 days agoHandshake completed214 ms
14 days agoHandshake completed222 ms
14 days agoHandshake completed233 ms
15 days agoHandshake completed160 ms
17 days agoHandshake completed166 ms
19 days agoHandshake completed180 ms
21 days agoHandshake completed185 ms
24 days agoHandshake completed176 ms
26 days agoHandshake completed168 ms
28 days agoHandshake completed173 ms

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

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