VS Code EchelonGraph CVE & Exposure search_vendor_advisories
How to: VS Code EchelonGraph CVE & Exposure search_vendor_advisories
Add EchelonGraph CVE & Exposure to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"echelongraph-mcp": {
"type": "http",
"url": "https://mcp.echelongraph.io/mcp"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something search_vendor_advisories does. VS Code lists the server's tools on connect and calls search_vendor_advisories itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that EchelonGraph CVE & Exposure's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Set these first
EchelonGraph CVE & Exposure will not start until these are set, so search_vendor_advisories never becomes available.
-
ECHELONGRAPH_API_BASE -
ECHELONGRAPH_API_TIMEOUT_MS
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 4 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.