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
193 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 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 completed193 ms
1 day agoHandshake completed114 ms
2 days agoHandshake completed120 ms
3 days agoHandshake completed64 ms
4 days agoHandshake completed47 ms
5 days agoHandshake completed53 ms
6 days agoHandshake completed135 ms
9 days agoHandshake completed47 ms
11 days agoHandshake completed72 ms
14 days agoHandshake completed42 ms
16 days agoHandshake completed93 ms
18 days agoHandshake completed61 ms
20 days agoHandshake completed59 ms
22 days agoHandshake completed61 ms
25 days agoHandshake completed45 ms
26 days agoHandshake completed59 ms
28 days agoHandshake completed41 ms
29 days agoHandshake completed122 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 Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) and makes no claim about it beyond what these checks measured.