Remote MCP · Endpoint

CISA Known Exploited Vulnerabilities (kevwatch) MCP server

No. CISA Known Exploited Vulnerabilities (kevwatch) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/cisa-known-exploited-vulnerabilities-kevwatch-aedaf3/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-cisa-known-exploited-vulnerability-catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
CISA KEV catalog: active-exploit alerts, hourly. Register in-session — free testnet funds.
Listing
From the official MCP registry (active).
Recent checks of CISA Known Exploited Vulnerabilities (kevwatch)
CheckedResultHandshake
2 hours agoHandshake completed159 ms
2 days agoHandshake completed172 ms
4 days agoHandshake completed188 ms
6 days agoHandshake completed309 ms
7 days agoHandshake completed114 ms
8 days agoHandshake completed137 ms
9 days agoHandshake completed538 ms
12 days agoHandshake completed1.29 s
14 days agoHandshake completed464 ms
15 days agoHandshake completed303 ms
17 days agoHandshake completed461 ms
18 days agoHandshake completed372 ms
19 days agoHandshake completed289 ms
20 days agoHandshake completed480 ms
20 days agoHandshake completed277 ms
22 days agoHandshake completed388 ms
23 days agoHandshake completed381 ms

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

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 CISA Known Exploited Vulnerabilities (kevwatch) and makes no claim about it beyond what these checks measured.