Remote MCP · Endpoint

KI-Radar24 MCP server

No. KI-Radar24 answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://ki-radar24.de/mcp

The last check completed an MCP handshake.

Registry name
de.ki-radar24/ki-radar24
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
389 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find AI tools, AI agencies and AI freelancers in Europe from the KI-Radar24 directory.
Listing
From the official MCP registry (active).
Recent checks of KI-Radar24
CheckedResultHandshake
56 minutes agoHandshake completed389 ms
3 days agoHandshake completed385 ms
12 days agoHandshake completed612 ms
13 days agoHandshake completed533 ms
14 days agoHandshake completed525 ms
15 days agoHandshake completed638 ms
17 days agoHandshake completed581 ms
18 days agoHandshake completed483 ms
18 days agoHandshake completed465 ms
20 days agoHandshake completed532 ms
22 days agoHandshake completed458 ms
25 days agoHandshake completed513 ms
27 days agoHandshake completed478 ms
29 days agoHandshake completed491 ms

The last 14 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 KI-Radar24 and makes no claim about it beyond what these checks measured.