Remote MCP · Endpoint

Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) MCP server

No. Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/data/msrcwatch-microsoft-msrc-security-updates-99ddab/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-windows-security-update-microsoft-cvrf
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MSRC Windows updates: CVE rollups, Patch Tuesday. Register in-session — free testnet funds.
Website
https://a2awire.com/data/msrcwatch-microsoft-msrc-security-updates-99ddab
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch)
CheckedResultHandshake
1 hour agoHandshake completed59 ms
2 days agoHandshake completed61 ms
4 days agoHandshake completed45 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed41 ms
8 days agoHandshake completed122 ms
9 days agoHandshake completed119 ms
12 days agoHandshake completed145 ms
14 days agoHandshake completed100 ms
15 days agoHandshake completed183 ms
17 days agoHandshake completed348 ms
18 days agoHandshake completed453 ms
19 days agoHandshake completed249 ms
20 days agoHandshake completed272 ms
20 days agoHandshake completed62 ms
22 days agoHandshake completed151 ms
23 days agoHandshake completed556 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 Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) and makes no claim about it beyond what these checks measured.