Black Duck Security Scanner
NPM · @BLACK-DUCK/MCP-SERVER · 2 COMPONENTS
AI-powered security scanning using Black Duck Signal for vulnerability detection.
Available components
Last scanned (1 minute ago)
Scores higher than 0% of npm servers
Category Security
Recent critical change
CVE-2026-102829 affects this package (9 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security73
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 49 of 147 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 110 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Oct 26 −34
- CVE-2026-102829 affects this package: high ▼ critical
- CVE-2026-102828 affects this package: high ▼ critical
- Score status: scored → failed ▼ critical
- Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
- CVE-2026-101904 no longer affects this package ▲ security
- CVE-2026-101898 no longer affects this package ▲ security
- CVE-2026-67318 no longer affects this package ▲ security
- CVE-2026-101900 no longer affects this package ▲ security
- CVE-2026-101899 no longer affects this package ▲ security
- CVE-2026-101903 no longer affects this package ▲ security
- CVE-2026-101909 no longer affects this package ▲ security
- CVE-2026-101908 no longer affects this package ▲ security
- CVE-2026-67313 no longer affects this package ▲ security
- CVE-2026-67317 no longer affects this package ▲ security
- CVE-2026-67320 no longer affects this package ▲ security
- CVE-2026-67321 no longer affects this package ▲ security
- CVE-2026-67319 no longer affects this package ▲ security
- CVE-2026-101906 no longer affects this package ▲ security
- CVE-2026-101902 no longer affects this package ▲ security
- CVE-2026-67314 no longer affects this package ▲ security
- CVE-2026-67315 no longer affects this package ▲ security
- CVE-2026-101901 no longer affects this package ▲ security
- CVE-2026-67316 no longer affects this package ▲ security
- CVE-2026-101905 no longer affects this package ▲ security
- CVE-2026-67312 no longer affects this package ▲ security
- 1 Oct 26 34
- CVE-2026-101905 affects this package: high ▼ security
- CVE-2026-101906 affects this package: high ▼ security
- CVE-2026-101902 affects this package: high ▼ security
- CVE-2026-101904 affects this package: high ▼ security
- CVE-2026-101901 affects this package: high ▼ security
- CVE-2026-101909 affects this package: high ▼ security
- CVE-2026-101898 affects this package: high ▼ security
- CVE-2026-101903 affects this package: high ▼ security
- CVE-2026-101908 affects this package: high ▼ security
- CVE-2026-101899 affects this package: high ▼ security
- CVE-2026-101900 affects this package: high ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Security disclosure: fail → pass ▲ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Aug 26 0
- GHSA-frvp-7c67-39w9 no longer affects this package ▲ security
- 12 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@black-duck/mcp-server@1.1.8
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 32 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-v5rq-49vh-5v5c | CVE-2026-102829 | critical | yes | |
| GHSA-3pq3-5fj3-cg6v | CVE-2026-101898 | high | yes | |
| GHSA-42h9-826w-cgv3 | CVE-2026-67313 | medium | yes | |
| GHSA-44g4-m2mj-wpvx | CVE-2026-101899 | medium | yes | |
| GHSA-4hqw-qxg8-jxx2 | CVE-2026-101900 | medium | yes | |
| GHSA-542g-h47m-68v8 | CVE-2026-101901 | high | yes | |
| GHSA-7q8q-rj6j-mhjq | CVE-2026-67319 | medium | yes | |
| GHSA-9fr6-4gfg-395g | CVE-2026-101902 | medium | yes | |
| GHSA-c29m-xwm3-cm6r | CVE-2026-101903 | high | yes | |
| GHSA-f4gw-2p7v-4548 | CVE-2026-67315 | medium | yes | |
| GHSA-gcfj-64vw-6mp9 | CVE-2026-67320 | high | yes | |
| GHSA-hcpx-6fm6-wx23 | CVE-2026-67321 | medium | yes | |
| GHSA-j8rh-479h-cp32 | CVE-2026-101904 | medium | yes | |
| GHSA-jqh4-m9w3-8hp9 | CVE-2026-67317 | medium | yes | |
| GHSA-m8m8-qj5v-23w3 | CVE-2026-101905 | high | yes | |
| GHSA-mghh-pgcx-3jjj | CVE-2026-101906 | high | yes | |
| GHSA-mmx7-hfxf-jppx | CVE-2026-67316 | medium | yes | |
| GHSA-mwf2-3pr3-8698 | CVE-2026-67318 | medium | yes | |
| GHSA-pmv8-rq9r-6j72 | CVE-2026-67312 | medium | yes | |
| GHSA-vh66-26gq-q6x8 | CVE-2026-101908 | medium | yes | |
| GHSA-x97p-jq2g-jp4f | CVE-2026-101909 | high | yes | |
| GHSA-xj6q-8x83-jv6g | CVE-2026-67314 | medium | yes | |
| GHSA-858h-whjf-mvg5 | CVE-2026-102827 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-g4wm-2vf7-vfgr | CVE-2026-102826 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-x6jw-m9v5-85vh | CVE-2026-102828 | critical | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 147 packages
| Packages resolved | 147 |
|---|---|
| Stale | 49 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the Black Duck Security Scanner MCP server?
Black Duck Security Scanner runs locally as an npm package, launched with npx -y @black-duck/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @black-duck/mcp-server
claude mcp add com-blackduck-mcp-server -- npx -y @black-duck/mcp-server
What is the Black Duck Security Scanner MCP server?
Black Duck Security Scanner is an MCP server listed in the public MCP registry as com.blackduck/mcp-server. AI-powered security scanning using Black Duck Signal for vulnerability detection. This page covers its npm package (@black-duck/mcp-server).
Is the Black Duck Security Scanner MCP server still maintained?
Black Duck Security Scanner is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Black Duck Security Scanner MCP server under?
Black Duck Security Scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.