Remote MCP · Endpoint

com.cve-security/cve-intelligence MCP server

No. com.cve-security/cve-intelligence answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cve-security.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.cve-security/cve-intelligence
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
CVE intelligence: exploitation (KEV/EPSS), detection coverage, fixed versions, CPE configurations.
Listing
From the official MCP registry (active).
Recent checks of com.cve-security/cve-intelligence
CheckedResultHandshake
1 hour agoHandshake completed135 ms
19 hours agoHandshake completed198 ms
2 days agoHandshake completed51 ms
3 days agoHandshake completed274 ms
4 days agoHandshake completed305 ms
5 days agoHandshake completed51 ms
6 days agoHandshake completed69 ms
7 days agoHandshake completed361 ms
10 days agoHandshake completed71 ms
13 days agoHandshake completed400 ms
15 days agoHandshake completed52 ms
17 days agoHandshake completed53 ms
19 days agoHandshake completed52 ms
21 days agoHandshake completed225 ms
23 days agoHandshake completed230 ms
25 days agoHandshake completed44 ms
27 days agoHandshake completed174 ms
28 days agoHandshake completed170 ms
29 days agoHandshake completed310 ms

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

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 com.cve-security/cve-intelligence and makes no claim about it beyond what these checks measured.