Remote MCP · Endpoint

Debian Security Advisories — buy per-query in-session (debianwatch) MCP server

No. Debian Security Advisories — buy per-query in-session (debianwatch) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/data/debian-security-advisories-05eb6d/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-debian-security-advisory-dsa-linux
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Debian Security Advisories (DSA). $0.01/query. Register in-session — free testnet funds.
Listing
From the official MCP registry (active).
Recent checks of Debian Security Advisories — buy per-query in-session (debianwatch)
CheckedResultHandshake
1 hour agoHandshake completed60 ms
1 day agoHandshake completed61 ms
2 days agoHandshake completed31 ms
3 days agoHandshake completed141 ms
4 days agoHandshake completed144 ms
5 days agoHandshake completed59 ms
6 days agoHandshake completed146 ms
9 days agoHandshake completed68 ms
12 days agoHandshake completed210 ms
14 days agoHandshake completed601 ms
16 days agoHandshake completed88 ms
18 days agoHandshake completed122 ms
20 days agoHandshake completed89 ms
22 days agoHandshake completed42 ms
25 days agoHandshake completed60 ms
26 days agoHandshake completed132 ms
28 days agoHandshake completed58 ms
29 days agoHandshake completed31 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.

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