INDIVIDUAL MCP TOOL
track
Start watching something in VulnTracker for the API key's team: a product (default; slug or id from search_products / check_dependencies matched_slug), a vendor, a single CVE, or a keyword.
LIVE ENDPOINT
https://api.vulntracker.io/mcp
Connect to this endpoint to inspect the live schema for track and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name, description or schema mentions credentials.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vulntracker]
url = "https://api.vulntracker.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vulntracker": {
"type": "http",
"url": "https://api.vulntracker.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vulntracker
Remote MCP URL: https://api.vulntracker.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vulntracker": {
"url": "https://api.vulntracker.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vulntracker": {
"type": "http",
"url": "https://api.vulntracker.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vulntracker",
"transport": "streamable-http",
"url": "https://api.vulntracker.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
add_to_board— Add CVEs to the team's board (the API key's team) as cards, or update their status if a card already exists.check_dependencies— Check many product@version pairs in one call.check_version— The core question: which CVEs affect this exact version of a product, and which version fixes each?list_board_cards— The team's CVE board: the CVEs that reached this team (by tracking notification or added by hand), each with its triage status (new, acknowledged, in_progress, resolved, dismissed), resolution status, notes, severity and the vendor/product it was recorded against.list_trackings— The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.lookup_cve— Full record for one CVE: description, CVSS, EPSS, KEV/exploitation and SSVC, affected products with version ranges and fixes from the ledger, vendor advisories (CSAF), public exploit repositories, and VulnTracker's remediation guide when one is published.product_cves— All CVEs recorded against a product in the affected-version ledger, newest first, with the version ranges each one names.product_versions— List the versions VulnTracker knows for a product, with per-version CVE and fix counts.