Remote MCP · Endpoint

Go Vulnerability Database Tracker — buy per-query in-session (govulnwatch) MCP server

No. Go Vulnerability Database Tracker — buy per-query in-session (govulnwatch) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/data/govulnwatch-go-vulnerability-database-tracker-dac615/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-go-vulnerability-golang-security
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
72 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Go vulns: CVEs per module, fixed versions. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/govulnwatch-go-vulnerability-database-tracker-dac615
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Go Vulnerability Database Tracker — buy per-query in-session (govulnwatch)
CheckedResultHandshake
1 hour agoHandshake completed72 ms
2 days agoHandshake completed93 ms
4 days agoHandshake completed96 ms
5 days agoHandshake completed77 ms
7 days agoHandshake completed75 ms
8 days agoHandshake completed195 ms
9 days agoHandshake completed81 ms
12 days agoHandshake completed60 ms
13 days agoHandshake completed67 ms
15 days agoHandshake completed49 ms
16 days agoHandshake completed49 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed40 ms
20 days agoHandshake completed66 ms
20 days agoHandshake completed74 ms
21 days agoHandshake completed34 ms
23 days agoHandshake completed54 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 Go Vulnerability Database Tracker — buy per-query in-session (govulnwatch) and makes no claim about it beyond what these checks measured.