{"id":"io.vulntracker/mcp","slug":"io-vulntracker-mcp","title":"VulnTracker","description":"CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.","version":"2.5.0","publisher":{"kind":"domain","id":"vulntracker.io","label":"vulntracker.io","url":"https://vulntracker.io"},"website":"https://vulntracker.io","repository":"https://github.com/vulntracker/vulntracker-mcp","remotes":[{"type":"streamable-http","url":"https://api.vulntracker.io/mcp","headers":[{"description":"VulnTracker API key as a bearer token. Create one at https://vulntracker.io/settings/api-keys (free account: 30 read-only calls a day).","isRequired":true,"value":"Bearer {api_key}","isSecret":true,"variables":{"api_key":{"description":"API key starting with vt_","isRequired":true,"isSecret":true}},"name":"Authorization"}]}],"packages":[],"published":"2026-11-10","updated":"2026-11-10","status":"online","auth":"","latency_ms":1432,"checked":"2026-11-19","uptime":67,"checks":3,"tools":[{"name":"add_to_board","title":"Add CVEs to the board","description":"Add 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 findings on the board; write which dependency and version each CVE came from into notes. Up to 50 CVE ids per call, counted as one tool call. Ask the user before adding; never add unmatched or needs_confirmation findings without saying so.","read_only":false},{"name":"check_dependencies","title":"Check a dependency list","description":"Check many product@version pairs in one call. Give the dependencies you read from the repository's manifests (go.mod, package.json / lock files, requirements.txt, pom.xml, Gemfile.lock, Cargo.lock, Dockerfile base images). For each one you get whether VulnTracker matched a product, whether the exact version is known, how many CVEs affect it, the newest affected CVEs with fix versions, and how conf","read_only":true},{"name":"check_version","title":"Check an installed version","description":"The 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 evidence, confidence and fix versions, and (b) range_affected_cves: CVEs whose source gave a version range that contains this version (e.g. '3.0.0 to before 3.0.8'); affected_total adds both. all_versions_cves lists records whose source named no ","read_only":true},{"name":"create_jira_issue","title":"Create Jira issue","description":"Open 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 the card already has an issue, returns that one with existing=true. Only when the user asks.","read_only":false},{"name":"list_board_cards","title":"List board cards","description":"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. Use it to answer 'what is open on our board', 'which cards mention product X', or to find the card for a CVE.","read_only":true},{"name":"list_trackings","title":"List trackings","description":"The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.","read_only":true},{"name":"lookup_cve","title":"Look up a CVE","description":"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.","read_only":true},{"name":"product_cves","title":"List a product's CVEs","description":"All CVEs recorded against a product in the affected-version ledger, newest first, with the version ranges each one names. entry_kind 'affected' = the product itself is vulnerable; 'runs_on_platform' = another product is vulnerable when running on it.","read_only":true},{"name":"product_versions","title":"List product versions","description":"List 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.","read_only":true},{"name":"remediation_guide","title":"Remediation guide","description":"VulnTracker's published remediation guide for a CVE: summary, steps, workarounds, caveats, kind (fix / workaround / guidance) and the fix versions it rests on. Returns has_guide=false when none is published.","read_only":true},{"name":"search_cves","title":"Search CVEs","description":"Search 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 (at most 10 pages per filter set, so narrow the filters instead of walking the whole database). 'tracked_only' limits to CVEs matching the API key's team trackings.","read_only":true},{"name":"search_products","title":"Search products","description":"Find VulnTracker products (software, firmware, libraries) by name. Returns slugs to use with check_version, product_versions and product_cves. Searches display names and known aliases (package names, CPE tokens).","read_only":true},{"name":"track","title":"Track a product, vendor, CVE or keyword","description":"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. New CVEs matching the tracking reach the team's board and its notification channels. Plan tracking limits apply; the error says so when the limit is reached. Use when the user asks to 'track', 'watch' or 'follo","read_only":false},{"name":"untrack","title":"Stop tracking","description":"Remove 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.","read_only":false},{"name":"update_board_card","title":"Update a board card","description":"Change one board card: triage status (new, acknowledged, in_progress, resolved, dismissed), resolution (patched, mitigated, workaround, accepted_risk, false_positive), notes and resolution notes. Creates the card if the CVE is not on the board yet. Use when the user says a CVE is fixed, accepted or a false positive.","read_only":false}],"server_info":{"name":"vulntracker","title":"VulnTracker","version":"dev"},"category":"ecommerce","tags":["finance","project","web-search"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-10","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/io-vulntracker-mcp/"}