Remote MCP · Endpoint

Dependency Vulnerability Tracker — package security advisories ($0.01/query) MCP server

No. Dependency Vulnerability Tracker — package security advisories ($0.01/query) answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/ghsawatch-package-dependency-vulnerabilities-malicious-package-advisories-d21673/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-dependency-vulnerability-malicious-package-security
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Dependency vulns & malicious-package advisories. Register in-session — free testnet funds.
Website
https://a2awire.com/data/ghsawatch-package-dependency-vulnerabilities-malicious-package-advisories-d21673
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Dependency Vulnerability Tracker — package security advisories ($0.01/query)
CheckedResultHandshake
2 hours agoHandshake completed78 ms
2 days agoHandshake completed47 ms
4 days agoHandshake completed36 ms
6 days agoHandshake completed77 ms
7 days agoHandshake completed51 ms
8 days agoHandshake completed34 ms
9 days agoHandshake completed571 ms
12 days agoHandshake completed465 ms
14 days agoHandshake completed363 ms
15 days agoHandshake completed188 ms
17 days agoHandshake completed217 ms
18 days agoHandshake completed392 ms
19 days agoHandshake completed81 ms
20 days agoHandshake completed520 ms
20 days agoHandshake completed395 ms
22 days agoHandshake completed359 ms
23 days agoHandshake completed437 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 Dependency Vulnerability Tracker — package security advisories ($0.01/query) and makes no claim about it beyond what these checks measured.