← Registry

Security & Testing

vulntracker.io

An MCP server for vulnerability tracking that checks CVEs affecting product versions, manages team CVE boards, and monitors tracked vendors, products, and keywords.

1 endpoint14 known toolsFirst detected November 10, 2026Last detected November 10, 2026

ENDPOINT 1

https://api.vulntracker.io/mcp

No auth detected

MCP server metadata

Name
vulntracker
Version
dev
Capabilities
loggingprompts.listChangedtools.listChanged
Server instructions

VulnTracker gives you vulnerability intelligence backed by an affected-version ledger: for a product and an exact version it tells you which CVEs apply and which version fixes each. When the user asks to check a repository, project or dependency list for vulnerabilities ("check this repo with VulnTracker", "are we exposed", "scan dependencies"): 1. Read the manifests and lock files (go.mod/go.sum, package-lock.json/yarn.lock/pnpm-lock.yaml, requirements.txt/poetry.lock, pom.xml/build.gradle, Gemfile.lock, Cargo.lock, composer.lock, *.csproj, Dockerfile FROM lines). Lock files hold the resolved versions. 2. Call check_dependencies with the name@version pairs (up to 50 per call). Never answer from memory. 3. For vulnerable items call lookup_cve on the CVEs that matter (CISA KEV first, then critical/high) and quote fix versions with their fix_stated_by_source flag. 4. Report a table (dependency, version, affected CVEs, worst severity, in CISA KEV, fix version), then concrete upgrade edits, then unmatched names. Offer to apply upgrades and open a PR; do not edit files before the user agrees. The scan_dependencies prompt contains the same procedure. Writing: add_to_board puts CVEs on the team's board (up to 50 per call, with notes saying which dependency and version each came from), update_board_card changes a card's status or resolution, track / untrack start or stop watching a product, vendor, CVE or keyword. These write to the team the API key belongs to; the response names that team. Only write when the user asks ("add these to the board", "track these dependencies", "mark it resolved"), tell them which team you wrote to, and never add unmatched or needs_confirmation findings without saying so. Prefer tracking products over single CVEs; plan limits apply and the error text explains them. For a single product use search_products to get the slug, then check_version. lookup_cve returns the full record for one CVE: scores, exploitation (KEV/EPSS/SSVC), affected products with version ranges, vendor advisories and, when VulnTracker has published one, a remediation guide. list_board_cards is the team's triage board; list_trackings is what the team watches. Read the flags: fix_stated_by_source=false means the fix version was derived from a range bound, not stated by the vendor; version_scheme="git" means the version is a commit id, not comparable to a release number; match_confidence tells you how a package was matched: "token" and "exact" are reliable, "name" is a whole-name search hit, "fallback" means an ecosystem-less product with the same word; such items carry needs_confirmation=true, are excluded from the vulnerable count, and must not be reported as findings unless matched_vendor confirms they are the same project (an npm "oauth" is not MediaWiki). all_versions_cves are records whose source named no version; shadowed_range_cves are records where an open-start "< X" entry sits next to an "A..X" entry with the same end X, so it may be the same branch restated without its start; an open-start entry with its own end is a separate release line and is counted. Neither is counted; report them only after checking the ranges or the advisory.

Known tools 14

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.

Potential side effects
check_dependencies

Check many product@version pairs in one call.

Inferred read-only
check_version

The core question: which CVEs affect this exact version of a product, and which version fixes each?

Inferred read-only
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.

Inferred read-only
list_trackings

The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.

Inferred read-only
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.

Inferred read-only
product_cves

All CVEs recorded against a product in the affected-version ledger, newest first, with the version ranges each one names.

Inferred read-only
product_versions

List the versions VulnTracker knows for a product, with per-version CVE and fix counts.

Inferred read-only
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.

Inferred read-only
search_cves

Search the CVE list with filters.

Inferred read-only
search_products

Find VulnTracker products (software, firmware, libraries) by name.

Inferred read-only
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.

Inferred read-only
untrack

Remove a tracking from the API key's team: give the same type and target used with track (or shown by list_trackings).

Potential side effects
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.

Inferred read-only

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.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for vulntracker.io was fetched 2026-11-11T02:21:25.288Z.

Trust status Trusted

vulntracker.io is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.