Remote MCP · Endpoint

Kulturbase MCP server

No. Kulturbase answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kulturbase.no/mcp

The last check completed an MCP handshake.

Registry name
no.kulturbase/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
287 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and discover currently playable Nordic cultural recordings.
Listing
From the official MCP registry (active).
Recent checks of Kulturbase
CheckedResultHandshake
1 hour agoHandshake completed287 ms
2 days agoHandshake completed200 ms
4 days agoHandshake completed232 ms
5 days agoHandshake completed211 ms
7 days agoHandshake completed350 ms
8 days agoHandshake completed275 ms
9 days agoHandshake completed619 ms
12 days agoHandshake completed243 ms
13 days agoHandshake completed238 ms
15 days agoHandshake completed234 ms
17 days agoHandshake completed216 ms
18 days agoHandshake completed172 ms
19 days agoHandshake completed207 ms
20 days agoHandshake completed271 ms
21 days agoHandshake completed178 ms
21 days agoHandshake completed532 ms
23 days agoHandshake completed185 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 Kulturbase and makes no claim about it beyond what these checks measured.