Fencer Intel vulnerability feed
Free merged CVE, GHSA and OSV feed: search, a live feed, a lockfile check and data reports.
我該用這個嗎
品質與安全性
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"intel": {
"url": "https://intel.fencer.dev/mcp"
}
}
}遠端端點
https://intel.fencer.dev/mcpstreamable-http它能做什麼
工具清單
工具(5)
🟢search(q, severity, kev, exploited, tech, ...)
Search Fencer Intel entries (CVE, GHSA and OSV advisories merged into one entry per vulnerability). Free text in `q` matches ids, titles, descriptions, vendors, products and package names; structured parameters narrow the result. `published` is the CVE publish date. `listed_since` is when the entry became news here, and `kev_added_since` is the day CISA added it to KEV (both an ISO date or timestamp; a KEV time cuts on that UTC day). Each result says why it matched; when nothing matches, `broader` lists relaxed queries that do return results.
輸入結構描述
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Free text, an exact id such as CVE-2021-44228 or GHSA-jfh8-c2jp-5v3q, or a name a vulnerability is known by (Log4Shell, Heartbleed)."
},
"severity": {
"type": "array",
"items": {
"type": "string",
"enum": [
"critical",
"high",
"medium",
"low",
"none"
]
},
"description": "Severities to include."
},
"kev": {
"type": "boolean",
"description": "Only entries in the CISA Known Exploited Vulnerabilities catalog."
},
"exploited": {
"type": "boolean",
"description": "Only entries known exploited (KEV) or with a public exploit (Exploit-DB or Metasploit)."
},
"tech": {
"type": "array",
"items": {
"type": "string",
"enum": [
"nextjs",
"react",
"node",
"express",
"django",
"flask",
"rails",
"spring",
"log4j",
"java",
"kubernetes",
"docker",
"nginx",
"apache-httpd",
"openssl",
"postgresql",
"mysql",
"redis",
"microsoft-sql-server",
"oracle-database",
"mariadb",
"ibm-db2",
"mongodb",
"sap-ase",
"php",
"dotnet",
"powershell",
"python",
"go",
"rust",
"ruby",
"perl",
"erlang",
"deno",
"bun",
"npm",
"pnpm",
"yarn",
"mise",
"uv",
"pip",
"tomcat",
"struts",
"weblogic",
"activemq",
"coldfusion",
"safari",
"firefox",
"curl",
"openssh",
"sudo",
"git",
"gitea",
"gogs",
"grafana",
"elastic",
"drupal",
"laravel",
"craft-cms",
"langflow",
"atlassian",
"teamcity",
"artifactory",
"github-enterprise-server",
"argo-cd",
"imagemagick",
"glibc",
"bash",
"wordpress",
"jenkins",
"gitlab",
"fortinet",
"citrix",
"ivanti",
"cisco-ios",
"palo-alto-panos",
"vmware",
"microsoft-exchange",
"chrome",
"linux-kernel"
]
},
"description": "Technologies."
},
"ecosystem": {
"type": "array",
"items": {
"type": "string",
"enum": [
"npm",
"pypi",
"go",
"maven",
"crates.io",
"packagist",
"rubygems",
"hex",
"nuget",
"github-actions",
"pub",
"swift",
"hackage",
"ghc",
"cran",
"opam",
"julia",
"bitnami"
]
},
"description": "Package ecosystems."
},
"vendor": {
"type": "string",
"description": "Vendor or product name, matched from the start of a word (\"micro\" finds Microsoft), e.g. \"fortinet\"."
},
"package": {
"type": "string",
"description": "Exact package name, e.g. \"lodash\" or \"org.apache.logging.log4j:log4j-core\"."
},
"published": {
"type": "string",
"description": "CVE publish date: 2024, 2024-05, 2024-01-01 (that day), 2024-01-01..2024-03-31, >=2024-01-01, <2024-01-01, or a relative window such as 1d or 30d. Anything else is an error."
},
"listed_since": {
"type": "string",
"description": "ISO date or timestamp. Only entries whose `listed` (when the entry became news here, not its publish date) is at or after it."
},
"kev_added_since": {
"type": "string",
"description": "ISO date or timestamp. Only entries CISA added to KEV on or after that UTC day (2026-11-08T15:00:00Z keeps 2026-11-08). With no `q`, no `listed_since` and no `sort`, results are ordered by that date, then id; an explicit `sort` wins."
},
"type": {
"type": "string",
"enum": [
"cve",
"ghsa",
"osv"
],
"description": "Id family of the entry."
},
"sort": {
"type": "string",
"enum": [
"relevance",
"newest",
"severity",
"epss"
],
"description": "Order. relevance (default with q): matches in the id, title, products or packages first, then in CISA KEV, critical, newest. newest (default without q), severity, or epss (most likely exploited first)."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 50,
"default": 10
}
}
}🟢get_vulnerability(id)
Full entry for a CVE, GHSA or OSV id: description, CVSS, CISA KEV status, due date, and ransomware use (kev.ransomware is true only for Known; kev.ransomwareUse is known, unknown or none), EPSS score and the date it first reached 10%, public exploits (Exploit-DB, Metasploit), affected packages with fixed versions, affected products, references and source records; where known, ATT&CK techniques (attack), ransomware groups (ransomware) and the Project Zero zero-day listing (zeroDay); vendorAdvisories holds vendor CSAF advisories and VEX statements (CISA, Red Hat): per product affected, fixed or not affected, with the remediation and a link (keep the credit of each with it); maintainerAdvisory links the advisory the maintainers published on their GitHub repository and says whether it is unreviewed (GitHub has not reviewed it yet, so the affected packages and versions are the maintainers’ word); inferredPackages (only when no record lists packages) are npm or PyPI packages inferred because a CVE product has the package’s name and the CVE references the GitHub repository the package’s registry entry names: low confidence, say "probably" and that no advisory lists them.
輸入結構描述
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "CVE-…, GHSA-… or an OSV id (PYSEC-…, GO-…, RUSTSEC-…)."
}
},
"required": [
"id"
]
}🟢list_feed(filter, tech, ecosystem, vendor, listed_since, ...)
Newest entries of a feed, the same as the /feed endpoint, ordered by `listed`: when the entry became news here (its publish date, or later if it reached us late or turned critical later). `filter`: critical = in CISA KEV, or CISA SSVC exploitation "active", or CVSS 9+ in a listed technology (WordPress plugins and themes excepted; WordPress itself counts), or CVSS 7+ with EPSS ≥ 0.1; kev = in CISA KEV (ordered by date added). `listed_since` keeps entries whose `listed` is at or after an ISO date or timestamp; with `filter` kev alone the cut is the KEV day, which is what that list sorts by. `kev_added_since` keeps entries CISA added to KEV on or after that UTC day, and orders the list by that date unless `listed_since` is also set. An entry must match any value of a field and every field given.
輸入結構描述
{
"type": "object",
"properties": {
"filter": {
"type": "array",
"items": {
"type": "string",
"enum": [
"critical",
"kev"
]
},
"description": "Feed filters."
},
"tech": {
"type": "array",
"items": {
"type": "string",
"enum": [
"nextjs",
"react",
"node",
"express",
"django",
"flask",
"rails",
"spring",
"log4j",
"java",
"kubernetes",
"docker",
"nginx",
"apache-httpd",
"openssl",
"postgresql",
"mysql",
"redis",
"microsoft-sql-server",
"oracle-database",
"mariadb",
"ibm-db2",
"mongodb",
"sap-ase",
"php",
"dotnet",
"powershell",
"python",
"go",
"rust",
"ruby",
"perl",
"erlang",
"deno",
"bun",
"npm",
"pnpm",
"yarn",
"mise",
"uv",
"pip",
"tomcat",
"struts",
"weblogic",
"activemq",
"coldfusion",
"safari",
"firefox",
"curl",
"openssh",
"sudo",
"git",
"gitea",
"gogs",
"grafana",
"elastic",
"drupal",
"laravel",
"craft-cms",
"langflow",
"atlassian",
"teamcity",
"artifactory",
"github-enterprise-server",
"argo-cd",
"imagemagick",
"glibc",
"bash",
"wordpress",
"jenkins",
"gitlab",
"fortinet",
"citrix",
"ivanti",
"cisco-ios",
"palo-alto-panos",
"vmware",
"microsoft-exchange",
"chrome",
"linux-kernel"
]
},
"description": "Technologies."
},
"ecosystem": {
"type": "array",
"items": {
"type": "string",
"enum": [
"npm",
"pypi",
"go",
"maven",
"crates.io",
"packagist",
"rubygems",
"hex",
"nuget",
"github-actions",
"pub",
"swift",
"hackage",
"ghc",
"cran",
"opam",
"julia",
"bitnami"
]
},
"description": "Package ecosystems."
},
"vendor": {
"type": "string",
"description": "Vendor or product name, matched from the start of a word, e.g. \"fortinet\" or \"exchange server\"."
},
"listed_since": {
"type": "string",
"description": "ISO date or timestamp. Only entries whose `listed` is at or after it. With `filter` kev alone, the list is ordered by the KEV date and the cut is that day."
},
"kev_added_since": {
"type": "string",
"description": "ISO date or timestamp. Only entries CISA added to KEV on or after that UTC day. Orders the list by that date unless `listed_since` is also set. Page with `cursor` to read the whole window."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 100,
"default": 20
},
"cursor": {
"type": "string",
"description": "next_cursor from a previous call."
}
}
}🟢check_stack(lockfile, filename, packages)
Check exact package versions for known vulnerabilities. Pass a lockfile's contents (package-lock.json, bun.lock, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, Cargo.lock, go.sum, Gemfile.lock, composer.lock, mix.lock, packages.lock.json, gradle.lockfile, .github/workflows/*.yml, action.yml, pubspec.lock, Package.resolved, renv.lock, Manifest.toml, cabal.project.freeze, *.opam.locked) with its filename, an SBOM (CycloneDX JSON, SPDX 2 JSON, Syft JSON, e.g. from `syft <image> -o cyclonedx-json`; up to 10 MB) in the same field, or a package list. An SBOM's language packages are checked like a lockfile's; its OS packages (deb, apk, rpm and Arch alpm purls) are matched against the distro advisories for their release and come back in "os" (findings with the fixed version per package; releases with no advisories on file are marked unchecked, never guessed, and Arch-based distros such as Manjaro as unchecked "derivative"; a finding or package with possible: true comes from Arch's tracker, which gives no introduced version, so the version may predate the bug: say "may be affected"; keep the license objects of share-alike distro data with it). A language finding with unreviewed: true was matched on the maintainers' own GitHub advisory, or on the packages a CVE record names when its CNA's scope covers them, which GitHub has not reviewed yet: say so. A finding with inferred: true was matched on a package inferred from the CVE's product name and repository (no advisory lists the package), by the CVE's own version range: say it probably applies; unchecked items with reason "inferred" are such packages whose CVE gives no versions to compare, and with reason "maintainer" packages a maintainers' advisory names with a range Intel can't compare for that version, and with reason "cve" packages a CVE record names whose versions don't decide that one: say they may be affected. A GitHub Actions workflow or action.yml works too: each uses: owner/repo@ref is checked, a floating tag (v4) as the newest release of its line; refs pinned to a commit SHA (without a "# v1.2.3" comment) or a branch come back in "unchecked" with the advisories on file. Also lists versions endoflife.date marks as out of support (eol). No matches means none were found, not that the packages are safe.
輸入結構描述
{
"type": "object",
"properties": {
"lockfile": {
"type": "string",
"description": "Full text of the lockfile or SBOM."
},
"filename": {
"type": "string",
"description": "Lockfile name, e.g. \"package-lock.json\". Detected from content if omitted (SBOMs always are)."
},
"packages": {
"type": "array",
"description": "Alternatively, packages at exact versions.",
"items": {
"type": "object",
"properties": {
"ecosystem": {
"type": "string",
"enum": [
"npm",
"pypi",
"go",
"maven",
"crates.io",
"packagist",
"rubygems",
"hex",
"nuget",
"github-actions",
"pub",
"swift",
"hackage",
"ghc",
"cran",
"opam",
"julia",
"bitnami"
]
},
"name": {
"type": "string"
},
"version": {
"type": "string"
}
},
"required": [
"ecosystem",
"name",
"version"
]
}
}
}
}🟡report_feedback(kind, message, id, tool)
Send a report to the Fencer Intel team: an entry with wrong data (severity, affected or fixed versions, packages, KEV, EPSS), a vulnerability or fix the feed is missing, or a tool that returned something wrong. Use it only when the user asks to report something, or agrees to a report you propose. Say what you saw, where (the entry id, or the tool and the arguments you passed), what you expected, and a source link when you have one. Never include secrets, credentials, lockfile contents or personal data: people read every report, and it is kept for 365 days. If the call returns an error, the report was not saved. Nobody replies, so it is not a way to ask a question. At most 5 reports per 60 seconds.
輸入結構描述
{
"type": "object",
"properties": {
"kind": {
"type": "string",
"enum": [
"wrong_data",
"missing_entry",
"missing_fix",
"tool_problem",
"other"
],
"description": "wrong_data: an entry says something wrong. missing_entry: a vulnerability the feed lacks. missing_fix: a fixed version the feed lacks. tool_problem: a tool failed or answered wrongly. other: anything else."
},
"message": {
"type": "string",
"minLength": 10,
"maxLength": 4000,
"description": "What is wrong or missing, what you expected, and a source link when you have one."
},
"id": {
"type": "string",
"description": "The CVE, GHSA or OSV id the report is about, if any."
},
"tool": {
"type": "string",
"enum": [
"search",
"get_vulnerability",
"list_feed",
"check_stack"
],
"description": "The tool the report is about, if any."
}
},
"required": [
"kind",
"message"
]
}社群
證據