VulnTracker
CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger
What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: review pull requests.Similar tools
Listed for the same task: review pull requestsReviews
No review yet. Used VulnTracker? Be the first to help others choose.What it does
VulnTracker is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as review pull requests or scan code for vulnerabilities.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 23h ago (live check)Hosted endpoint
https://api.vulntracker.io/mcpstreamable-http
Required: Authorization (get it from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"vulntracker": {
"url": "https://api.vulntracker.io/mcp",
"headers": {
"Authorization": "<your Authorization>"
}
}
}
}Replace the values in <angle brackets>.
Live check
Electra Index connected to the hosted endpoint 23h agoONLINE VulnTracker answered an MCP connection on 16 Nov 2026 and introduced itself as vulntracker dev (MCP protocol 2025-06-18).
15 tools offered to AI assistants
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. 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 nocheck_dependencies· 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 youcheck_version· 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 sourcecreate_jira_issue· 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 uslist_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/productlist_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 onproduct_cves· 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 runnproduct_versions· 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.remediation_guide· 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.search_cves· 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 whsearch_products· 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).
Show 3 more
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. New CVEs matching the tracking reach the team's bountrack· 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.update_board_card· 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 bo
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://api.vulntracker.io/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://vulntracker.io | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/vulntracker/vulntracker-mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 2.5.0 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- NEW10 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is VulnTracker still online?
Free alerts · no account▲ 0Do you run VulnTracker? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about VulnTracker
How do I connect VulnTracker?
Use the hosted endpoint https://api.vulntracker.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does VulnTracker need an API key or token?
Yes. The registry entry lists a required value: Authorization. Get it from the publisher.
What tools does VulnTracker offer?
When Electra Index connected on 16 Nov 2026, it listed 15 tools: add_to_board, check_dependencies, check_version, create_jira_issue, list_board_cards, list_trackings, lookup_cve, product_cves and more. The full list is in "Live check" above.
Is VulnTracker online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 23h ago.
What can I use VulnTracker for?
Based on its description, it is most relevant to: review pull requests, scan code for vulnerabilities.