Skip to main content
Glama

Fencer Intel vulnerability feed

Server Details

Free merged CVE, GHSA and OSV feed with search, a live feed, and a lockfile check.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a clearly distinct role: check_stack scans lockfiles/SBOMs, get_vulnerability fetches one entry by id, list_feed returns newest feed entries, and search queries the corpus. The only mild overlap is between list_feed and search, since both can return entry sets, but the descriptions make the boundary (chronological feed with filters vs. free-text/structured query) clear enough.

Naming Consistency4/5

Three tools follow a clean verb_noun pattern (check_stack, get_vulnerability, list_feed), while 'search' is a bare verb without a noun. That single deviation is readable and unlikely to cause misuse, but it keeps the set from being fully uniform.

Tool Count4/5

Four tools is a tight, well-scoped surface for a vulnerability intel feed: scan, lookup, browse, and search. It is slightly lean—no dedicated package-name lookup or bulk export—but nothing feels redundant or missing at the count level.

Completeness4/5

The read-only intel lifecycle is well covered: discovering entries (list_feed/search), drilling into a CVE/GHSA/OSV (get_vulnerability), and scanning real dependency manifests/SBOMs (check_stack). Minor gaps exist—e.g. no explicit 'all vulnerabilities affecting package X' endpoint or pagination/export affordance—but agents can work around these via search.

Publisher details

Operator
Fencer Inc
Operator website
https://intel.fencer.dev
Vendor relationship
First-party
Trust center
Not available
Restrictions
Free Service

Available Tools

4 tools
check_stackCheck dependenciesAInspect

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.

Inputs: filename, lockfile, packages.

get_vulnerabilityGet one vulnerabilityBInspect

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.

Inputs: id (required).

list_feedList a feedAInspect

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.

Inputs: tech, limit, cursor, filter, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables vulnerability lookup and triage across NVD, EPSS, CISA KEV, OSV, and many other sources, while tracking an estate's exposure changes from SBOMs and lockfiles through snapshots and prioritized diffs.
      32
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables auditing npm, pip, and other package dependencies for known CVEs via the OSV database, with tools to scan manifests, query individual packages, and integrate into CI/CD workflows.
      570 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources