VulnTracker MCP server
io.vulntracker/mcpvulntracker.iostreamable-httpv2.5.0Scanned
CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.
14 tools: 1 can delete or cancel things, 7 change things and 6 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the VulnTracker MCP server can do
The VulnTracker MCP server is published by vulntracker.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: untrack) and create or change data (7 tools: add_to_board, check_dependencies, check_version, product_cves and 3 more). 6 tools only read.
2 tools read private data (list_board_cards and lookup_cve).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 2.5.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 1Claude Code: deny
untrackRemove a tracking from the API key's team: give the same type and target used with track (or shown by list_trackings).1 finding
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "untrack" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true}; The description's first verb is "remove": a word for removing or ending something.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: false
- title: Stop tracking
Changes things 7Claude Code: ask
add_to_boardAdd CVEs to the team's board (the API key's team) as cards, or update their status if a card already exists.No findings
Why it is in this group
- The name "add_to_board" says "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: false
- title: Add CVEs to the board
check_dependenciesCheck many product@version pairs in one call.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Check a dependency list
check_versionThe core question: which CVEs affect this exact version of a product, and which version fixes each?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Check an installed version
product_cvesAll CVEs recorded against a product in the affected-version ledger, newest first, with the version ranges each one names.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: List a product's CVEs
remediation_guideVulnTracker's published remediation guide for a CVE: summary, steps, workarounds, caveats, kind (fix / workaround / guidance) and the fix versions it rests on.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Remediation guide
trackStart 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…No findings
Why it is in this group
- The description's first verb is "start": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: false
- title: Track a product, vendor, CVE or keyword
update_board_cardChange one board card: triage status (new, acknowledged, in_progress, resolved, dismissed), resolution (patched, mitigated, workaround, accepted_risk, false_positive), notes and re…No findings
Why it is in this group
- The name "update_board_card" says "update": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- readOnlyHint: false
- title: Update a board card
Only reads 6Show 6 read-only tools
list_board_cardsThe 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)…Reads private dataNo findings
Why it is in this group
- The name "list_board_cards" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: List board cards
list_trackingsThe vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.No findings
Why it is in this group
- The name "list_trackings" says "list": a word for reading.
Description, as the server wrote it The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: List trackings
lookup_cveFull 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 explo…Reads private dataNo findings
Why it is in this group
- The name "lookup_cve" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "repository": it reads repositories.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Look up a CVE
product_versionsList the versions VulnTracker knows for a product, with per-version CVE and fix counts.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: List product versions
search_cvesSearch the CVE list with filters.No findings
Why it is in this group
- The name "search_cves" says "search": a word for reading.
Description, as the server wrote it Search the CVE list with filters. Results are newest first. 'tracked_only' limits to CVEs matching the API key's team trackings.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Search CVEs
search_productsFind VulnTracker products (software, firmware, libraries) by name.No findings
Why it is in this group
- The name "search_products" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Search products
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 destructive, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.vulntracker.io/mcp: tools/list returned 15 tools to an anonymous client, including untrack (destructive), add_to_board (write), check_dependencies (write), check_version (write), create_jira_issue (write) and 4 more
Posture changes
- Nov 17, 2026
- Tools that change things, listed without credentials: 8 to 9
Findings
Matches of fixed checks, with the text they matched.
- Warnuntrack
The server marks "untrack" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true}; The description's first verb is "remove": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 9.View diff
- Tools that change things, listed without credentials: 8 to 9
Install
Pinned to version 2.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vulntracker https://api.vulntracker.io/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http vulntracker https://api.vulntracker.io/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vulntracker__list_board_cards",
"mcp__vulntracker__list_trackings",
"mcp__vulntracker__lookup_cve",
"mcp__vulntracker__product_versions",
"mcp__vulntracker__search_cves",
"mcp__vulntracker__search_products"
],
"ask": [
"mcp__vulntracker__add_to_board",
"mcp__vulntracker__check_dependencies",
"mcp__vulntracker__check_version",
"mcp__vulntracker__product_cves",
"mcp__vulntracker__remediation_guide",
"mcp__vulntracker__track",
"mcp__vulntracker__update_board_card"
],
"deny": [
"mcp__vulntracker__untrack"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vulntracker. Review it before you use it.
Capability tags behind 2 rules
- mcp__vulntracker__list_board_cards private-data
- mcp__vulntracker__lookup_cve private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.vulntracker/mcp/verify?hash=e46bf2d0055c463194929744c4a5075581127dbf30483456f2c29e282c9dcfaf" | jq -e '.changed == false'Pinned hash e46bf2d0055c, from Nov 10, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.vulntracker/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.vulntracker/mcp)Source: MCP Registry · repository. Synced Nov 10, 2026, 08:18 UTC.
VulnTracker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the VulnTracker MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the VulnTracker MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: untrack.
Can the VulnTracker MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the VulnTracker MCP server have?
- 14 tools: 1 destructive, 7 write, 6 read. untrack, add_to_board, check_dependencies, check_version, product_cves, remediation_guide, track, update_board_card and 6 more.
Does the VulnTracker MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the VulnTracker MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the VulnTracker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.