← Registry tracker

Black Duck Security Scanner

AI-powered security vulnerability scanning via Black Duck Signal.

Category
Security
Primary Subcategory
Pending
View in the Claude registry
Integration details

Description

Black Duck MCP brings Signal's AI-powered security analysis directly into Claude Desktop. Scan git changes, individual files, or full projects for security vulnerabilities. Results are exposed as MCP resources for detailed AI-driven analysis. Note: scanned source content is transmitted to Black Duck's remote analysis endpoint for processing.

Integration type
Connector
Verification status
Verified connector
Platform
Claude
Category
Security

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Pending

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Brand
Black Duck
Access
Unknown
First tracked
2026-07-30
Tool count
2
Geography
US

Get alerts for Black Duck Security Scanner

Get updates when Black Duck Security Scanner’s Discoverability Score or category rank changes.

Claude Discoverability Score

Black Duck Security Scanner isn’t discoverable through Claude’s Connector picker

It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.

No spam. Unsubscribe any time.

No spam. Unsubscribe any time.

What the current score measures

Claude showing a list of relevant Connectors in a conversation

Remote Connectors Claude can surface from the Connector picker.

How this score is measured
Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Black Duck Security Scanner has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.
Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
Tools

2 tools agents can invoke

Black Duck Security Scanner FAQ
How do I improve a Verified connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.