Remote MCP · Endpoint

KrakenShield MCP server

No. KrakenShield answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://api.krakenshield.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.krakenshield/krakenshield
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
352 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Quick HTTPS/SSL check of any website, cybersecurity glossary and KrakenShield prices.
Listing
From the official MCP registry (active).
Recent checks of KrakenShield
CheckedResultHandshake
9 hours agoHandshake completed352 ms
4 days agoHandshake completed535 ms
14 days agoHandshake completed366 ms
15 days agoHandshake completed351 ms
15 days agoHandshake completed329 ms
17 days agoHandshake completed353 ms
18 days agoHandshake completed344 ms
19 days agoHandshake completed345 ms
20 days agoHandshake completed349 ms
21 days agoHandshake completed351 ms
23 days agoHandshake completed346 ms
26 days agoHandshake completed338 ms
28 days agoHandshake completed342 ms

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