Remote MCP · Endpoint

Gulvbuddy prisestimat MCP server

No. Gulvbuddy prisestimat answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://www.gulvbuddy.dk/mcp

The last check completed an MCP handshake.

Registry name
dk.gulvbuddy/prisestimat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
143 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Prisestimat på nyt trægulv og gulvafslibning i Danmark samt dækningstjek. Gratis, uden login.
Listing
From the official MCP registry (active).
Recent checks of Gulvbuddy prisestimat
CheckedResultHandshake
19 minutes agoHandshake completed143 ms
10 days agoHandshake completed182 ms
10 days agoHandshake completed176 ms
11 days agoHandshake completed148 ms
13 days agoHandshake completed233 ms
14 days agoHandshake completed468 ms
14 days agoHandshake completed440 ms
15 days agoHandshake completed304 ms
17 days agoHandshake completed298 ms
19 days agoHandshake completed1.58 s
21 days agoHandshake completed197 ms
24 days agoHandshake completed156 ms
26 days agoHandshake completed186 ms
28 days agoHandshake completed516 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 Gulvbuddy prisestimat and makes no claim about it beyond what these checks measured.