io.vulntracker/mcp
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
VulnTracker
Publisher-provided description
CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.
Summary by lookupd
Look up CVEs, affected and fixed versions for dependencies, and manage a team board of vulnerability triage cards and tracking.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http mcp https://api.vulntracker.io/mcp
Codex, remote (streamable-http)
codex mcp add mcp --url https://api.vulntracker.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://api.vulntracker.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (15 tools)
Publisher-provided text
add_to_boardAdd CVEs to the team's board (the API key's team) as cards, or update their status if a card already exists. Use after a scan when the user asks to put the findcheck_dependenciesCheck many product@version pairs in one call. Give the dependencies you read from the repository's manifests (go.mod, package.json / lock files, requirements.txcheck_versionThe core question: which CVEs affect this exact version of a product, and which version fixes each? Returns (a) CVEs whose claims name this version, with evidencreate_jira_issueOpen a Jira issue for a CVE on the team's board (the card is created first if missing) using the team's Jira integration. Returns the issue key and URL; if thelist_board_cardsThe 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,list_trackingsThe vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.lookup_cveFull record for one CVE: description, CVSS, EPSS, KEV/exploitation and SSVC, affected products with version ranges and fixes from the ledger, vendor advisoriesproduct_cvesAll CVEs recorded against a product in the affected-version ledger, newest first, with the version ranges each one names. entry_kind 'affected' = the product itproduct_versionsList the versions VulnTracker knows for a product, with per-version CVE and fix counts. Use to find the exact version string before calling check_version.remediation_guideVulnTracker's published remediation guide for a CVE: summary, steps, workarounds, caveats, kind (fix / workaround / guidance) and the fix versions it rests on.search_cvesSearch the CVE list with filters. Results are newest first, up to 100 per call; when has_more is true pass next_cursor back as 'cursor' for the following page (search_productsFind VulnTracker products (software, firmware, libraries) by name. Returns slugs to use with check_version, product_versions and product_cves. Searches displaytrackStart watching something in VulnTracker for the API key's team: a product (default; slug or id from search_products / check_dependencies matched_slug), a vendoruntrackRemove a tracking from the API key's team: give the same type and target used with track (or shown by list_trackings). Board cards stay.update_board_cardChange one board card: triage status (new, acknowledged, in_progress, resolved, dismissed), resolution (patched, mitigated, workaround, accepted_risk, false_pos
Details
- Version: 2.5.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 1060 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/vulntracker/vulntracker-mcp
- Website: https://vulntracker.io
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.vulntracker/mcp)
- 62092 servers
- Last crawl: 2026-11-11T17:38:11.606Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp