Is it blocked at the edge yet?

Connect to the Vigilbase CVE MCP server (https://cve.vigilbase.com/mcp, streamable HTTP, no key needed) and use it for vulnerability triage:
1. Scan my lockfiles with scan_dependencies and list the vulnerable packages, exploited-in-the-wild CVEs first, then ones with public exploit code.
2. For each of those CVEs, call get_cve_coverage: tell me whether my WAF vendor claims a rule, whether it blocks by default, and what Vigilbase's own lab test measured.
3. Run check_exposure for my domain on the top CVEs.
4. Give me a prioritised fix list with the fixed versions, and cite the source URLs the server returns.

claude mcp add --transport http vigilbase-cve https://cve.vigilbase.com/mcp

{
  "mcpServers": {
    "vigilbase-cve": {
      "url": "https://cve.vigilbase.com/mcp"
    }
  }
}

# ~/.codex/config.toml
[mcp_servers.vigilbase-cve]
url = "https://cve.vigilbase.com/mcp"

https://cve.vigilbase.com/mcp