Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VulnTracker

REMOTE · API.VULNTRACKER.IO

CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.

+3 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3241 tokens (~216/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_version” rewrote its description, which is the text the model reads security
  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • New tool “create_jira_issue” functional
  • 10 Nov 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.vulntracker.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vulntracker.io CN=WE1,O=Google Trust Services,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA256 4b4a3c161ee273431340855a109a03cf
SANs: vulntracker.io, *.vulntracker.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.vulntracker.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
vulntracker.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.vulntracker.io/mcp Verified 200
http (plaintext) http://api.vulntracker.io/mcp HTTPS enforced 301 https://api.vulntracker.io/mcp
MCP tools · 15 exposed · ~2,411 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_to_board ~197

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.

NameTypeReqDescription
cve_idsarrayyesCVE ids, e.g. ["CVE-2026-1234", "CVE-2026-2345"] (max 50)
notesstring–Note written on every card, e.g. 'found by dependency scan of repo X: lodash 4.17.20'
statusstring–Card status for all listed CVEs: new (default), acknowledged, in_progress, resolved, dismissed

No output schema declared.

No examples provided.

check_dependencies ~121

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.

NameTypeReqDescription
itemsarrayyesDependencies to check

No output schema declared.

No examples provided.

check_version ~426

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.

NameTypeReqDescription
limitinteger–Max CVEs (default 50, max 200)
productstringyesProduct slug or id
rolestring–'affected' (CVEs affecting this version), 'fix' (CVEs this version fixes) or empty for both
versionstringyesExact version string as the product publishes it, e.g. '3.0.7', '7.4.2'

No output schema declared.

No examples provided.

create_jira_issue ~101

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.

NameTypeReqDescription
cve_idstringyesCVE id
notestring–Optional note for the issue description, e.g. which dependency and version it came from

No output schema declared.

No examples provided.

list_board_cards ~281

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.

NameTypeReqDescription
archivedboolean–Show archived cards instead of the live board
exploitedboolean–Only cards whose CVE is in CISA KEV (same as kev)
kevboolean–Only cards whose CVE is in CISA KEV
limitinteger–Max cards (default 20, max 50)
pageinteger–Page number, 1-based
querystring–CVE id prefix (CVE-2026-12) or free text matched against vendor/product/vulnerability name
remediationstring–Only cards with a published VulnTracker guide of this kind: fix, workaround, guidance
severitystring–critical, high, medium, low (comma-separated)
statusstring–Comma-separated card statuses: new, acknowledged, in_progress, resolved, dismissed. Empty = all non-archived

No output schema declared.

No examples provided.

list_trackings ~35

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_cve ~90

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.

NameTypeReqDescription
cve_idstringyesCVE id, e.g. CVE-2026-1234

No output schema declared.

No examples provided.

product_cves ~122

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.

NameTypeReqDescription
entry_kindstring–'affected', 'affected_device', 'runs_on_platform' or empty for all
limitinteger–Max CVEs (default 50, max 200)
offsetinteger–Pagination offset
productstringyesProduct slug or id

No output schema declared.

No examples provided.

product_versions ~94

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.

NameTypeReqDescription
limitinteger–Max results (default 50, max 200)
productstringyesProduct slug (from search_products) or product id
searchstring–Optional substring to filter versions, e.g. '3.0'

No output schema declared.

No examples provided.

remediation_guide ~70

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.

NameTypeReqDescription
cve_idstringyesCVE id

No output schema declared.

No examples provided.

search_cves ~277

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.

NameTypeReqDescription
cursorstring–next_cursor from the previous search_cves answer, with the same filters
exploitedboolean–Only CVEs in CISA KEV (is_exploited). SSVC exploitation (poc / active) is a separate field on lookup_cve
limitinteger–Max results (default 20, max 100)
productstring–Product name filter
published_afterstring–YYYY-MM-DD
published_beforestring–YYYY-MM-DD
querystring–Free text matched against CVE id prefix or vulnerability name
remediationstring–Only CVEs with a published VulnTracker guide of this kind: fix, workaround, guidance
severitystring–critical, high, medium, low
tracked_onlyboolean–Only CVEs matching this account's trackings
vendorstring–Vendor name filter

No output schema declared.

No examples provided.

search_products ~112

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).

NameTypeReqDescription
limitinteger–Max results (default 10, max 50)
querystringyesProduct or package name, e.g. 'openssl', 'log4j', 'fortios'
vendorstring–Optional vendor slug or name to narrow the search

No output schema declared.

No examples provided.

track ~246

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.

NameTypeReqDescription
exploited_onlyboolean–Only notify when the CVE has known exploitation
min_severityinteger–Minimum severity to notify for: 0 all, 1 low, 2 medium, 3 high, 4 critical. Omit for the team default
notesstring–Optional note, e.g. 'used by repo X'
targetstringyesProduct/vendor slug or id, CVE id, or keyword text
typestring–product (default), vendor, cve or keyword
version_filterstring–Optional version filter for a product, e.g. '>=3.0'

No output schema declared.

No examples provided.

untrack ~79

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.

NameTypeReqDescription
targetstringyesProduct/vendor slug or id, CVE id, or keyword text
typestring–product (default), vendor, product_version, cve or keyword

No output schema declared.

No examples provided.

update_board_card ~160

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.

NameTypeReqDescription
cve_idstringyesCVE id
notesstring–Card notes (appended as the card's notes)
resolution_notesstring–How it was resolved
resolution_statusstring–patched, mitigated, workaround, accepted_risk, false_positive
statusstring–new, acknowledged, in_progress, resolved, dismissed

No output schema declared.

No examples provided.

Install

How do I install the VulnTracker MCP server?

VulnTracker is a hosted endpoint at https://api.vulntracker.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.vulntracker.io

# add to Claude Code
claude mcp add --transport http io-vulntracker-mcp 'https://api.vulntracker.io/mcp'
Common questions

What is the VulnTracker MCP server?

VulnTracker is an MCP server listed in the public MCP registry as io.vulntracker/mcp. CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger. This page covers its hosted endpoint (https://api.vulntracker.io/mcp).

Is the VulnTracker MCP server safe to use?

VulnTracker scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VulnTracker MCP server expose?

VulnTracker exposes 15 tools: add_to_board, check_dependencies, check_version, create_jira_issue, list_board_cards, and 10 more. Their descriptions and schemas cost roughly 2,411 tokens of context every time the server is loaded.

Does the VulnTracker MCP server require authentication?

No. We connected to VulnTracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VulnTracker MCP server still maintained?

VulnTracker is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the VulnTracker MCP server?

VerifyMCP ran 13 checks on VulnTracker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.