Endpoints: 76,849MCP servers: 32,722Payout addresses: 3,825Paid calls: 6,104Letters: 83Defects: 3,890counted 3 min ago
teppi

MCP serverio.vulntracker/mcp

CVEs, affected versions and fix versions for your dependencies, from an affected-version ledger.
UNRATEDActivestreamable-httpapi.vulntracker.io

Overview

Score?
UNRATED 0.114
of what a free look can see, on 5 looks
Looks
5
last 6 hr ago
Tools
15
changed 5 days ago

More info

URL
api.vulntracker.io/mcp
streamable-http
Says it is
vulntracker dev
protocol 2025-06-18
In the record since
7 days ago

Among servers32,722 with a card

0median 0.547 · this server 0.114 · highest on record 0.8351

Toolsfrom sha256:f8d027ed92…d6ea3b · +0 −0 5 days ago

The tools this server lists, read out of the definition it returned
ToolSchema
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; w
input · no output
check_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.
input · no output
check_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 f
input · no output
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
input · no output
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)
input · no output
list_trackings
The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.
input · no output
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 explo
input · no output
product_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;
input · no output
product_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.
input · no output
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=fa
input · no output
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
input · no output
search_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 alia
input · no output
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
input · no output
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.
input · no output
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 re
input · no output
Verify it yourselfnpx teppi-check https://api.vulntracker.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M74JEVQNEY1ARFEXQF8JSV3Y