Remote MCP · Endpoint

secureIT Sicherheits-Checks MCP server

No. secureIT Sicherheits-Checks answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://secureit.icu/mcp

The last check completed an MCP handshake.

Registry name
icu.secureit/security-checks
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
401 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Kostenlose Sicherheits-Checks ohne Konto: SPF/DKIM/DMARC, Mails, Links, Webseiten, Passwort-Leaks.
Listing
From the official MCP registry (active).
Recent checks of secureIT Sicherheits-Checks
CheckedResultHandshake
5 hours agoHandshake completed401 ms
9 days agoHandshake completed420 ms
10 days agoHandshake completed399 ms
11 days agoHandshake completed398 ms
12 days agoHandshake completed388 ms
14 days agoHandshake completed382 ms
14 days agoHandshake completed382 ms
15 days agoHandshake completed396 ms
17 days agoHandshake completed365 ms
19 days agoHandshake completed378 ms
21 days agoHandshake completed384 ms
24 days agoHandshake completed376 ms
26 days agoHandshake completed368 ms
28 days agoHandshake completed371 ms

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

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