Remote MCP · Endpoint

CVE Risk Check MCP server

No. CVE Risk Check answered an MCP handshake 7 hours ago.

UpLast checked 7 hours 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
4.71 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 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
7 hours agoHandshake completed4.71 s
2 days agoHandshake completed156 ms
5 days agoHandshake completed535 ms
7 days agoHandshake completed417 ms
9 days agoHandshake completed187 ms
11 days agoHandshake completed302 ms
13 days agoHandshake completed49 ms
15 days agoHandshake completed44 ms
17 days agoHandshake completed742 ms
19 days agoHandshake completed63 ms
20 days agoHandshake completed931 ms
21 days agoHandshake completed33 ms
23 days agoHandshake completed283 ms

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

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.