Remote MCP · Endpoint

AIS CVE Priorities — daily exploit-ranked patch list for AI agents MCP server

No. AIS CVE Priorities — daily exploit-ranked patch list for AI agents answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://api.aislabs.ai/cve/mcp

The last check completed an MCP handshake.

Registry name
ai.aislabs/cve
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
219 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Daily CVE priorities ranked by real exploitation (KEV+EPSS) for AI agents; free teaser, paid full
Listing
From the official MCP registry (active).
Recent checks of AIS CVE Priorities — daily exploit-ranked patch list for AI agents
CheckedResultHandshake
10 hours agoHandshake completed219 ms
2 days agoHandshake completed169 ms
4 days agoHandshake completed40 ms
5 days agoHandshake completed46 ms
7 days agoHandshake completed55 ms
8 days agoHandshake completed211 ms
10 days agoHandshake completed217 ms
12 days agoHandshake completed92 ms
13 days agoHandshake completed151 ms
15 days agoHandshake completed170 ms
16 days agoHandshake completed35 ms
17 days agoHandshake completed147 ms
19 days agoHandshake completed34 ms
19 days agoHandshake completed126 ms
20 days agoHandshake completed195 ms
21 days agoHandshake completed34 ms
23 days agoHandshake completed279 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 AIS CVE Priorities — daily exploit-ranked patch list for AI agents and makes no claim about it beyond what these checks measured.