Remote MCP · Endpoint

GLØDI MCP server

No. GLØDI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://glodi.no/mcp

The last check completed an MCP handshake.

Registry name
no.glodi/public-catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
419 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find clinics, treatments, prices and free times on GLØDI in Norway, with booking links.
Listing
From the official MCP registry (active).
Recent checks of GLØDI
CheckedResultHandshake
1 hour agoHandshake completed419 ms
3 days agoHandshake completed379 ms
12 days agoHandshake completed413 ms
13 days agoHandshake completed159 ms
15 days agoHandshake completed403 ms
15 days agoHandshake completed370 ms
17 days agoHandshake completed422 ms
18 days agoHandshake completed391 ms
18 days agoHandshake completed372 ms
20 days agoHandshake completed440 ms
22 days agoHandshake completed389 ms
25 days agoHandshake completed401 ms
27 days agoHandshake completed426 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 GLØDI and makes no claim about it beyond what these checks measured.