Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "vulntracker": {
      "type": "http",
      "url": "https://api.vulntracker.io/mcp",
      "headers": {
        "Authorization": "Bearer ${api_key}"
      }
    }
  }
}

claude mcp add --transport http vulntracker https://api.vulntracker.io/mcp --header "Authorization: Bearer ${api_key}"

[mcp_servers.vulntracker]
url = "https://api.vulntracker.io/mcp"
bearer_token_env_var = "api_key"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vulntracker": {
      "type": "remote",
      "url": "https://api.vulntracker.io/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:api_key}"
      }
    }
  }
}

{
  "mcpServers": {
    "vulntracker": {
      "type": "http",
      "url": "https://api.vulntracker.io/mcp",
      "headers": {
        "Authorization": "Bearer ${api_key}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=vulntracker&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLnZ1bG50cmFja2VyLmlvL21jcCIsImhlYWRlcnMiOnsiQXV0aG9yaXphdGlvbiI6IkJlYXJlciAke2FwaV9rZXl9In19"
}

{
  "servers": {
    "vulntracker": {
      "type": "http",
      "url": "https://api.vulntracker.io/mcp",
      "headers": {
        "Authorization": "Bearer ${api_key}"
      }
    }
  }
}

{
  "mcpServers": {
    "vulntracker": {
      "httpUrl": "https://api.vulntracker.io/mcp",
      "headers": {
        "Authorization": "Bearer ${api_key}"
      }
    }
  }
}

extensions:
  "vulntracker":
    enabled: true
    name: "vulntracker"
    type: streamable_http
    uri: "https://api.vulntracker.io/mcp"
    headers:
      "Authorization": "Bearer ${api_key}"
    timeout: 300

Placeholders to fill from your own secret store: ${api_key}. The registry never accepts secret values.

Quality 84 / 100new

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene81 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations15 of 15 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_trackings (destructiveHint, openWorldHint); lookup_cve (destructiveHint, openWorldHint); track (openWorldHint); …
pass
tools.token_costabout 3,396 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
pass
tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations

stabilityn/a · weight 15

n/a
stability.changes, stability.rug_pull, stability.new_linkstool history recorded for 3 of the 7 days needed

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

15 tools, about 3,396 tokens to load them all · tool set edd01746e8d2 · tools last changed 2026-11-12 · checked 2026-11-14 07:03 UTC

Tool changes

2026-11-12check_versionchangeddescription
before
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 version at all, and shadowed_range_cves lists records where only an open-start '< X' entry covers this version while the same record also has an 'A..X' entry ending at the same X (one source gave a start, the other did not; the open-start entry may just be the same branch restated). An open-start entry whose end differs from every bounded entry is its own release line (node '<= 20.20.1' beside 22/24 lines) and counts as affected; neither is in affected_total, both need confirmation. Fix objects carry provenance: quote a fix version with who stated it (stated_by, source_url); fix_stated_by_source=false / source="derived.range" means VulnTracker inferred the version from a range bound (derived_from), not a statement in the CVE record.
after · 90% of words in common
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 version at all, and shadowed_range_cves lists records where only an open-start '< X' entry covers this version while the same record also has an 'A..X' entry ending at the same X (one source gave a start, the other did not; the open-start entry may just be the same branch restated). An open-start entry whose end differs from every bounded entry is its own release line (node '<= 20.20.1' beside 22/24 lines) and counts as affected; neither is in affected_total, both need confirmation. Fix objects carry provenance: quote a fix version with who stated it (stated_by, source_url); fix_stated_by_source=false / source="derived.range" means VulnTracker inferred the version from a range bound (derived_from), not a statement in the CVE record. Fix objects may also carry stated_for (the stream or product the record named, e.g. a RHEL stream) and package (the package to update); when present, quote the package and stream, since on distributions the fix is a package version, not an OS version.
2026-11-12check_versionchangeddescription
before
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 version at all, and shadowed_range_cves lists records where only an open-start '< X' entry covers this version while the same record also has an 'A..X' entry ending at the same X (one source gave a start, the other did not; the open-start entry may just be the same branch restated). An open-start entry whose end differs from every bounded entry is its own release line (node '<= 20.20.1' beside 22/24 lines) and counts as affected; neither is in affected_total, both need confirmation. fix_stated_by_source=false means the fix version was derived from a range bound, not stated by the vendor.
after · 89% of words in common
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 version at all, and shadowed_range_cves lists records where only an open-start '< X' entry covers this version while the same record also has an 'A..X' entry ending at the same X (one source gave a start, the other did not; the open-start entry may just be the same branch restated). An open-start entry whose end differs from every bounded entry is its own release line (node '<= 20.20.1' beside 22/24 lines) and counts as affected; neither is in affected_total, both need confirmation. Fix objects carry provenance: quote a fix version with who stated it (stated_by, source_url); fix_stated_by_source=false / source="derived.range" means VulnTracker inferred the version from a range bound (derived_from), not a statement in the CVE record.
2026-11-10create_jira_issueadded
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.
2026-11-10search_cveschangeddescription, input schemameaning changed
before
Search the CVE list with filters. Results are newest first. 'tracked_only' limits to CVEs matching the API key's team trackings.
after · 41% of words in common
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.
2026-11-10list_board_cardschangedinput schema

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 100 / 100

provenance100

liveness100

freshness100

hygiene100

+repository +namespace-matches-repo +dns-namespace +website +reachable +uptime-100% +updated-4d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://api.vulntracker.io/mcp` streamable-http	api_key `${api_key}`	yes	100%	667 ms	2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05	2026-11-14

Tools (15)

`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 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.
`check_dependencies`read-only	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 confident the name match is. Max 50 items per call; batch larger lists.
`check_version`read-only	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 version at all, and shadowed_range_cves lists records where only an open-start '< X' entry covers this version while the same record also has an 'A..X' entry ending at the same X (one source gave a start, the other did not; the open-start entry may just be the same branch restated). An open-start entry whose end differs from every bounded entry is its own release line (node '<= 20.20.1' beside 22/24 lines) and counts as affected; neither is in affected_total, both need confirmation. Fix objects carry provenance: quote a fix version with who stated it (stated_by, source_url); fix_stated_by_source=false / source="derived.range" means VulnTracker inferred the version from a range bound (derived_from), not a statement in the CVE record. Fix objects may also carry stated_for (the stream or product the record named, e.g. a RHEL stream) and package (the package to update); when present, quote the package and stream, since on distributions the fix is a package version, not an OS version.
`create_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 user asks.
`list_board_cards`read-only	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.
`list_trackings`read-only	The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.
`lookup_cve`read-only	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`read-only	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.
`product_versions`read-only	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`read-only	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`read-only	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.
`search_products`read-only	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).
`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 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 'follow' the dependencies of a repository; prefer tracking products over individual CVEs.
`untrack`	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 board yet. Use when the user says a CVE is fixed, accepted or a false positive.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.vulntracker/mcp",
  "title": "VulnTracker",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json",
  "remotes": [
    {
      "url": "https://api.vulntracker.io/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "value": "Bearer {api_key}",
          "isSecret": true,
          "variables": {
            "api_key": {
              "isSecret": true,
              "isRequired": true,
              "description": "API key starting with vt_"
            }
          },
          "isRequired": true,
          "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)."
        }
      ]
    }
  ],
  "version": "2.5.0",
  "repository": {
    "url": "https://github.com/vulntracker/vulntracker-mcp",
    "source": "github"
  },
  "websiteUrl": "https://vulntracker.io",
  "description": "CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger."
}