Remote MCP · Endpoint

CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts) MCP server

No. CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/cisaalerts-cisa-cybersecurity-ics-advisories-55420c/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-cisa-advisory-ics-security-alert
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
CISA advisories & ICS alerts: new CVEs, remediation. Register in-session — free testnet funds.
Website
https://a2awire.com/data/cisaalerts-cisa-cybersecurity-ics-advisories-55420c
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts)
CheckedResultHandshake
2 hours agoHandshake completed73 ms
2 days agoHandshake completed160 ms
4 days agoHandshake completed142 ms
6 days agoHandshake completed127 ms
7 days agoHandshake completed90 ms
8 days agoHandshake completed45 ms
9 days agoHandshake completed2.08 s
12 days agoHandshake completed1.18 s
14 days agoHandshake completed458 ms
15 days agoHandshake completed348 ms
17 days agoHandshake completed257 ms
18 days agoHandshake completed447 ms
19 days agoHandshake completed306 ms
20 days agoHandshake completed461 ms
20 days agoHandshake completed507 ms
22 days agoHandshake completed449 ms
23 days agoHandshake completed303 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with CISA Cybersecurity & ICS Advisories — buy per-query in-session (cisaalerts) and makes no claim about it beyond what these checks measured.