Remote MCP · Endpoint

Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) MCP server

No. Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/bleepingwatch-cybersecurity-news-breach-alerts-522e02/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-cybersecurity-news-breach-alert
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
175 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Cybersecurity news & breach alerts: hacks, patches. Register in-session — free testnet funds.
Website
https://a2awire.com/data/bleepingwatch-cybersecurity-news-breach-alerts-522e02
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch)
CheckedResultHandshake
2 hours agoHandshake completed175 ms
1 day agoHandshake completed248 ms
2 days agoHandshake completed46 ms
3 days agoHandshake completed164 ms
4 days agoHandshake completed75 ms
5 days agoHandshake completed61 ms
6 days agoHandshake completed166 ms
9 days agoHandshake completed89 ms
12 days agoHandshake completed78 ms
14 days agoHandshake completed679 ms
16 days agoHandshake completed391 ms
18 days agoHandshake completed161 ms
20 days agoHandshake completed68 ms
23 days agoHandshake completed197 ms
25 days agoHandshake completed103 ms
26 days agoHandshake completed31 ms
28 days agoHandshake completed96 ms
29 days agoHandshake completed35 ms

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

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 Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) and makes no claim about it beyond what these checks measured.