Free merged CVE, GHSA and OSV feed with search, a live feed, and a lockfile check.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Lockfile name, e.g. "package-lock.json". Detected from content if omitted (SBOMs always are).
Full text of the lockfile or SBOM.
Alternatively, packages at exact versions.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http intel https://intel.fencer.dev/mcp
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.
| Argument | Type | Description |
|---|---|---|
| filename | string | Lockfile name, e.g. "package-lock.json". Detected from content if omitted (SBOMs always are). |
| lockfile | string | Full text of the lockfile or SBOM. |
| packages | array | Alternatively, packages at exact versions. |
{
"type": "object",
"properties": {
"filename": {
"type": "string",
"description": "Lockfile name, e.g. \"package-lock.json\". Detected from content if omitted (SBOMs always are)."
},
"lockfile": {
"type": "string",
"description": "Full text of the lockfile or SBOM."
},
"packages": {
"type": "array",
"items": {
"type": "object",
"required": [
"ecosystem",
"name",
"version"
],
"properties": {
"name": {
"type": "string"
},
"version": {
"type": "string"
},
"ecosystem": {
"enum": [
"npm",
"pypi",
"go",
"maven",
"crates.io",
"packagist",
"rubygems",
"hex",
"nuget",
"github-actions",
"pub",
"swift",
"hackage",
"ghc",
"cran",
"opam",
"julia",
"bitnami"
],
"type": "string"
}
}
},
"description": "Alternatively, packages at exact versions."
}
}
}Full entry for a CVE, GHSA or OSV id: description, CVSS, CISA KEV status and due date, 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.
| Argument | Type | Description |
|---|---|---|
| id* | string | CVE-…, GHSA-… or an OSV id (PYSEC-…, GO-…, RUSTSEC-…). |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "CVE-…, GHSA-… or an OSV id (PYSEC-…, GO-…, RUSTSEC-…)."
}
}
}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). An entry must match any value of a field and every field given.
| Argument | Type | Description |
|---|---|---|
| tech | array | Technologies. |
| limit | integer | |
| cursor | string | next_cursor from a previous call. |
| filter | array | Feed filters. |
| vendor | string | Vendor or product name, matched from the start of a word, e.g. "fortinet" or "exchange server". |
| ecosystem | array | Package ecosystems. |
{
"type": "object",
"properties": {
"tech": {
"type": "array",
"items": {
"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",
"glibc",
"bash",
"wordpress",
"jenkins",
"gitlab",
"fortinet",
"citrix",
"ivanti",
"cisco-ios",
"palo-alto-panos",
"vmware",
"microsoft-exchange",
"chrome",
"linux-kernel"
],
"type": "string"
},
"description": "Technologies."
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 100,
"minimum": 1
},
"cursor": {
"type": "string",
"description": "next_cursor from a previous call."
},
"filter": {
"type": "array",
"items": {
"enum": [
"critical",
"kev"
],
"type": "string"
},
"description": "Feed filters."
},
"vendor": {
"type": "string",
"description": "Vendor or product name, matched from the start of a word, e.g. \"fortinet\" or \"exchange server\"."
},
"ecosystem": {
"type": "array",
"items": {
"enum": [
"npm",
"pypi",
"go",
"maven",
"crates.io",
"packagist",
"rubygems",
"hex",
"nuget",
"github-actions",
"pub",
"swift",
"hackage",
"ghc",
"cran",
"opam",
"julia",
"bitnami"
],
"type": "string"
},
"description": "Package ecosystems."
}
}
}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. Each result says why it matched; when nothing matches, `broader` lists relaxed queries that do return results.
| Argument | Type | Description |
|---|---|---|
| q | string | Free text, or an exact id such as CVE-2021-44228 or GHSA-jfh8-c2jp-5v3q. |
| kev | boolean | Only entries in the CISA Known Exploited Vulnerabilities catalog. |
| tech | array | Technologies. |
| type | string | Id family of the entry. |
| limit | integer | |
| vendor | string | Vendor or product name, matched from the start of a word ("micro" finds Microsoft), e.g. "fortinet". |
| package | string | Exact package name, e.g. "lodash" or "org.apache.logging.log4j:log4j-core". |
| severity | array | Severities to include. |
| ecosystem | array | Package ecosystems. |
| exploited | boolean | Only entries known exploited (KEV) or with a public exploit (Exploit-DB or Metasploit). |
| published | string | 2024, 2024-05, 2024-01-01..2024-03-31, >=2024-01-01, <2024-01-01, or 30d. |
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Free text, or an exact id such as CVE-2021-44228 or GHSA-jfh8-c2jp-5v3q."
},
"kev": {
"type": "boolean",
"description": "Only entries in the CISA Known Exploited Vulnerabilities catalog."
},
"tech": {
"type": "array",
"items": {
"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",
"glibc",
"bash",
"wordpress",
"jenkins",
"gitlab",
"fortinet",
"citrix",
"ivanti",
"cisco-ios",
"palo-alto-panos",
"vmware",
"microsoft-exchange",
"chrome",
"linux-kernel"
],
"type": "string"
},
"description": "Technologies."
},
"type": {
"enum": [
"cve",
"ghsa",
"osv"
],
"type": "string",
"description": "Id family of the entry."
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 50,
"minimum": 1
},
"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\"."
},
"severity": {
"type": "array",
"items": {
"enum": [
"critical",
"high",
"medium",
"low",
"none"
],
"type": "string"
},
"description": "Severities to include."
},
"ecosystem": {
"type": "array",
"items": {
"enum": [
"npm",
"pypi",
"go",
"maven",
"crates.io",
"packagist",
"rubygems",
"hex",
"nuget",
"github-actions",
"pub",
"swift",
"hackage",
"ghc",
"cran",
"opam",
"julia",
"bitnami"
],
"type": "string"
},
"description": "Package ecosystems."
},
"exploited": {
"type": "boolean",
"description": "Only entries known exploited (KEV) or with a public exploit (Exploit-DB or Metasploit)."
},
"published": {
"type": "string",
"description": "2024, 2024-05, 2024-01-01..2024-03-31, >=2024-01-01, <2024-01-01, or 30d."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 18, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.