Server definition
- Hash
- sha256:f8d027ed92b13347e511a899fbac4f945a5b455f753511fb6fb12f2dfbd6ea3b
- What it is
- What a remote MCP server returned when asked what it offers: 15 tools
The blob, as servednamed by its sha256
{
"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.\n\nWhen the user asks to check a repository, project or dependency list for vulnerabilities (\"check this repo with VulnTracker\", \"are we exposed\", \"scan dependencies\"):\n1. 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.\n2. Call check_dependencies with the name@version pairs (up to 50 per call). Never answer from memory.\n3. For vulnerable items call lookup_cve on the CVEs that matter (CISA KEV first, then critical/high) and quote fix versions with who stated them (stated_by, source_url); a fix with fix_stated_by_source=false / source=\"derived.range\" was inferred from a range bound (derived_from), say so.\n4. 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.\nThe scan_dependencies prompt contains the same procedure.\n\nWriting: 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.\n\nFor 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.\n\nRead the flags: fix_stated_by_source=false / source=\"derived.range\" means VulnTracker inferred the fix version from a range bound (derived_from), not a statement in the CVE record; when true, stated_by names the CNA or ADP that stated it (often not the product's vendor) and source_url links the record; a fix object 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; 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.",
"tools": [
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"cve_ids": {
"description": "CVE ids, e.g. [\"CVE-2026-1234\", \"CVE-2026-2345\"] (max 50)",
"items": {
"type": "string"
},
"type": "array"
},
"notes": {
"description": "Note written on every card, e.g. 'found by dependency scan of repo X: lodash 4.17.20'",
"type": "string"
},
"status": {
"description": "Card status for all listed CVEs: new (default), acknowledged, in_progress, resolved, dismissed",
"type": "string"
}
},
"required": [
"cve_ids"
],
"type": "object"
},
"name": "add_to_board",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"items": {
"description": "Dependencies to check",
"items": {
"additionalProperties": false,
"properties": {
"ecosystem": {
"description": "Optional: npm, pypi, go, maven, cargo, rubygems, nuget, composer, docker",
"type": "string"
},
"name": {
"description": "Package or product name as it appears in the manifest, e.g. 'lodash', 'github.com/gin-gonic/gin', 'org.apache.logging.log4j:log4j-core', 'nginx'",
"type": "string"
},
"version": {
"description": "Installed version, e.g. '4.17.20' (strip ^ ~ v prefixes)",
"type": "string"
}
},
"required": [
"name",
"version"
],
"type": "object"
},
"maxItems": 50,
"type": "array"
}
},
"required": [
"items"
],
"type": "object"
},
"name": "check_dependencies",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"limit": {
"description": "Max CVEs (default 50, max 200)",
"type": "integer"
},
"product": {
"description": "Product slug or id",
"type": "string"
},
"role": {
"description": "'affected' (CVEs affecting this version), 'fix' (CVEs this version fixes) or empty for both",
"type": "string"
},
"version": {
"description": "Exact version string as the product publishes it, e.g. '3.0.7', '7.4.2'",
"type": "string"
}
},
"required": [
"product",
"version"
],
"type": "object"
},
"name": "check_version",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"cve_id": {
"description": "CVE id",
"type": "string"
},
"note": {
"description": "Optional note for the issue description, e.g. which dependency and version it came from",
"type": "string"
}
},
"required": [
"cve_id"
],
"type": "object"
},
"name": "create_jira_issue",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"archived": {
"description": "Show archived cards instead of the live board",
"type": "boolean"
},
"exploited": {
"description": "Only cards whose CVE is in CISA KEV (same as kev)",
"type": "boolean"
},
"kev": {
"description": "Only cards whose CVE is in CISA KEV",
"type": "boolean"
},
"limit": {
"description": "Max cards (default 20, max 50)",
"type": "integer"
},
"page": {
"description": "Page number, 1-based",
"type": "integer"
},
"query": {
"description": "CVE id prefix (CVE-2026-12) or free text matched against vendor/product/vulnerability name",
"type": "string"
},
"remediation": {
"description": "Only cards with a published VulnTracker guide of this kind: fix, workaround, guidance",
"type": "string"
},
"severity": {
"description": "critical, high, medium, low (comma-separated)",
"type": "string"
},
"status": {
"description": "Comma-separated card statuses: new, acknowledged, in_progress, resolved, dismissed. Empty = all non-archived",
"type": "string"
}
},
"type": "object"
},
"name": "list_board_cards",
"outputSchema": null
},
{
"description": "The vendors, products, versions, CVEs, keywords and CPEs this account's team is watching in VulnTracker.",
"inputSchema": {
"additionalProperties": false,
"properties": {},
"type": "object"
},
"name": "list_trackings",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"cve_id": {
"description": "CVE id, e.g. CVE-2026-1234",
"type": "string"
}
},
"required": [
"cve_id"
],
"type": "object"
},
"name": "lookup_cve",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"entry_kind": {
"description": "'affected', 'affected_device', 'runs_on_platform' or empty for all",
"type": "string"
},
"limit": {
"description": "Max CVEs (default 50, max 200)",
"type": "integer"
},
"offset": {
"description": "Pagination offset",
"type": "integer"
},
"product": {
"description": "Product slug or id",
"type": "string"
}
},
"required": [
"product"
],
"type": "object"
},
"name": "product_cves",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"limit": {
"description": "Max results (default 50, max 200)",
"type": "integer"
},
"product": {
"description": "Product slug (from search_products) or product id",
"type": "string"
},
"search": {
"description": "Optional substring to filter versions, e.g. '3.0'",
"type": "string"
}
},
"required": [
"product"
],
"type": "object"
},
"name": "product_versions",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"cve_id": {
"description": "CVE id",
"type": "string"
}
},
"required": [
"cve_id"
],
"type": "object"
},
"name": "remediation_guide",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"cursor": {
"description": "next_cursor from the previous search_cves answer, with the same filters",
"type": "string"
},
"exploited": {
"description": "Only CVEs in CISA KEV (is_exploited). SSVC exploitation (poc / active) is a separate field on lookup_cve",
"type": "boolean"
},
"limit": {
"description": "Max results (default 20, max 100)",
"type": "integer"
},
"product": {
"description": "Product name filter",
"type": "string"
},
"published_after": {
"description": "YYYY-MM-DD",
"type": "string"
},
"published_before": {
"description": "YYYY-MM-DD",
"type": "string"
},
"query": {
"description": "Free text matched against CVE id prefix or vulnerability name",
"type": "string"
},
"remediation": {
"description": "Only CVEs with a published VulnTracker guide of this kind: fix, workaround, guidance",
"type": "string"
},
"severity": {
"description": "critical, high, medium, low",
"type": "string"
},
"tracked_only": {
"description": "Only CVEs matching this account's trackings",
"type": "boolean"
},
"vendor": {
"description": "Vendor name filter",
"type": "string"
}
},
"type": "object"
},
"name": "search_cves",
"outputSchema": null
},
{
"description": "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).",
"inputSchema": {
"additionalProperties": false,
"properties": {
"limit": {
"description": "Max results (default 10, max 50)",
"type": "integer"
},
"query": {
"description": "Product or package name, e.g. 'openssl', 'log4j', 'fortios'",
"type": "string"
},
"vendor": {
"description": "Optional vendor slug or name to narrow the search",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "search_products",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"exploited_only": {
"description": "Only notify when the CVE has known exploitation",
"type": "boolean"
},
"min_severity": {
"description": "Minimum severity to notify for: 0 all, 1 low, 2 medium, 3 high, 4 critical. Omit for the team default",
"type": "integer"
},
"notes": {
"description": "Optional note, e.g. 'used by repo X'",
"type": "string"
},
"target": {
"description": "Product/vendor slug or id, CVE id, or keyword text",
"type": "string"
},
"type": {
"description": "product (default), vendor, cve or keyword",
"type": "string"
},
"version_filter": {
"description": "Optional version filter for a product, e.g. '>=3.0'",
"type": "string"
}
},
"required": [
"target"
],
"type": "object"
},
"name": "track",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"target": {
"description": "Product/vendor slug or id, CVE id, or keyword text",
"type": "string"
},
"type": {
"description": "product (default), vendor, product_version, cve or keyword",
"type": "string"
}
},
"required": [
"target"
],
"type": "object"
},
"name": "untrack",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"cve_id": {
"description": "CVE id",
"type": "string"
},
"notes": {
"description": "Card notes (appended as the card's notes)",
"type": "string"
},
"resolution_notes": {
"description": "How it was resolved",
"type": "string"
},
"resolution_status": {
"description": "patched, mitigated, workaround, accepted_risk, false_positive",
"type": "string"
},
"status": {
"description": "new, acknowledged, in_progress, resolved, dismissed",
"type": "string"
}
},
"required": [
"cve_id"
],
"type": "object"
},
"name": "update_board_card",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:f8d027ed92b13347e511a899fbac4f945a5b455f753511fb6fb12f2dfbd6ea3b | sha256sum