Remote MCP · Endpoint

CVE Risk Check MCP server

No. CVE Risk Check answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://cve.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/cve
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
163 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Triage a CVE: how severe it is, whether it is exploited, and how likely exploitation is.
Listing
From the official MCP registry (active).
Recent checks of CVE Risk Check
CheckedResultHandshake
44 minutes agoHandshake completed163 ms
3 days agoHandshake completed178 ms
13 days agoHandshake completed170 ms
13 days agoHandshake completed158 ms
15 days agoHandshake completed454 ms
15 days agoHandshake completed157 ms
17 days agoHandshake completed458 ms
18 days agoHandshake completed325 ms
18 days agoHandshake completed197 ms
20 days agoHandshake completed395 ms
22 days agoHandshake completed4.71 s
25 days agoHandshake completed156 ms
27 days agoHandshake completed535 ms
29 days agoHandshake completed417 ms

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

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 CVE Risk Check and makes no claim about it beyond what these checks measured.