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
68 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 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 completed68 ms
2 days agoHandshake completed197 ms
4 days agoHandshake completed103 ms
6 days agoHandshake completed31 ms
7 days agoHandshake completed96 ms
8 days agoHandshake completed35 ms
9 days agoHandshake completed366 ms
12 days agoHandshake completed1.20 s
14 days agoHandshake completed345 ms
15 days agoHandshake completed261 ms
17 days agoHandshake completed266 ms
18 days agoHandshake completed289 ms
19 days agoHandshake completed408 ms
20 days agoHandshake completed429 ms
20 days agoHandshake completed112 ms
22 days agoHandshake completed255 ms
23 days agoHandshake completed84 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 Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) and makes no claim about it beyond what these checks measured.