Black Duck Signal MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Black Duck Signal incremental and file security scans: Do change-scanning boundaries and uploaded source handling remain explicit as coding-assistant integrations expand?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Incremental or targeted AI-assisted application-security scans from coding agents.

What we know

Local Black Duck Signal MCP for scanning uncommitted/branch changes or selected files/directories and returning SARIF/report resources with remediation guidance.

Maintenance / activity evidence

@black-duck/mcp-server 1.1.8 published 2026-07-17T20:38:47.473Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read source/code-change scope and write local SARIF/log outputs. Writes: Write SARIF reports/log outputs.
Gateway API key.
Sensitive access: Proprietary source code, Vulnerability findings, Gateway key

Security scans require sending sensitive source to provider infrastructure; protect keys and egress.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do change-scanning boundaries and uploaded source handling remain explicit as coding-assistant integrations expand?

The bounded review of the publisher's documented Black Duck Signal incremental and file security scans and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Security scans require sending sensitive source to provider infrastructure; protect keys and egress.
Read source/code-change scope and write local SARIF/log outputs.
Gateway API key.
Source code and scan material are sent to Black Duck services; reports/logs remain locally accessible.
Reviewed write actions: Write SARIF reports/log outputs
Sensitive access: Proprietary source code, Vulnerability findings, Gateway key
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
public source repository identity
Requires Signal license, Node.js 24+ and outbound access to Black Duck endpoints.
Source code is submitted to Black Duck security services.
Changes scan depends on Git.
No public source repository was proven.

Original activity observations

@black-duck/mcp-server 1.1.8 published 2026-07-17T20:38:47.473Z

Technical identity

npm/@black-duck/mcp-server

Exact implementation source: https://www.npmjs.com/package/@black-duck/mcp-server ↗
Reviewed resource type: Testing / Debugging
Package identity: npm:@black-duck/mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@black-duck/mcp-server
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
documentation.blackduck.com/bundle/signal/page/topics/c_signal_overview.html
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.blackduck.com/signal-ai-appsec.html
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Testing / Debugging setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher supplies mcpServers stdio JSON and first scan workflow; verify service prerequisites in README.
publisher sdk or product install · Publisher instructions
npx -y @black-duck/mcp-server
Configure / authenticate
MCP100 setup guide
Publisher package metadata confirms bin `mcp-server` -> dist/index.js with Node.js >=24. Use publisher README mcpServers JSON to register exact npx launch; do not replace security scan tools with a fake read-only scan.
Check connection
Suggested check
Verify tool discovery; do not run `run_security_scan` on a private project just to test connection.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `radar-4b89fc0b13978d88a16a60ee6d2870023bb273711705325ae33f6080e7554596`, run `claude mcp remove radar-4b89fc0b13978d88a16a60ee6d2870023bb273711705325ae33f6080e7554596`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove radar-4b89fc0b13978d88a16a60ee6d2870023bb273711705325ae33f6080e7554596

Official Documentation & Sources

What it does

Local Black Duck Signal MCP for scanning uncommitted/branch changes or selected files/directories and returning SARIF/report resources with remediation guidance.

Capability: Security & Testing
Resource type: Testing / Debugging
Industry: Cybersecurity
Best fit: Incremental or targeted AI-assisted application-security scans from coding agents.

Representative uses

Scan uncommitted changes
Compare branch changes to main
Scan file/directory
Return SARIF issue counts/status/resources

Limitations

Requires Signal license, Node.js 24+ and outbound access to Black Duck endpoints.
Source code is submitted to Black Duck security services.
Changes scan depends on Git.
No public source repository was proven.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Gateway API key.
Permissions: Read source/code-change scope and write local SARIF/log outputs.
Data handling: Source code and scan material are sent to Black Duck services; reports/logs remain locally accessible.
Cost: license_required
Risk and cautions: Security scans require sending sensitive source to provider infrastructure; protect keys and egress.

Access scope and cautions

Write actions: Write SARIF reports/log outputs
Sensitive access: Proprietary source code Vulnerability findings Gateway key
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Scan uncommitted changes; Compare branch changes to main; Scan file/directory; Return SARIF issue counts/status/resources.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @black-duck/mcp-server. Recorded transport: stdio. Recorded environment-variable notes: BLACKDUCK_MCP_GATEWAY_KEY; BLACKDUCK_HOME (optional); BLACKDUCK_MCP_TOOL_TIMEOUT (optional); BLACKDUCK_MCP_LOG_LEVEL (optional). No configuration values are supplied here. Prerequisites: Node.js 24+; Signal license; outbound HTTPS; Git for changes scan. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Signal license plus gateway API key.

Can it modify data or perform write operations?

Documented write actions include: Write SARIF reports/log outputs. Recorded permission boundary: Read source/code-change scope and write local SARIF/log outputs.

What data-handling boundary should I consider?

Source code and scan material are sent to Black Duck services; reports/logs remain locally accessible. Recorded sensitive-access context: Proprietary source code; Vulnerability findings; Gateway key.

What limitations and risks should I check before use?

Security scans require sending sensitive source to provider infrastructure; protect keys and egress. Requires Signal license, Node.js 24+ and outbound access to Black Duck endpoints. Source code is submitted to Black Duck security services. Changes scan depends on Git. No public source repository was proven. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is license required. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.

Is this an official MCP?

Black Duck is listed as First-party MCP in MCP100’s current evidence.