Black Duck Security Scanner vs Vulnicheck
A side-by-side look at the Black Duck Security Scanner and Vulnicheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Black Duck Security Scanner for security work as a local process; choose Vulnicheck for security over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Black Duck Security Scanner when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BLACKDUCK_MCP_GATEWAY_KEY. - You want tools like
run_changes_security_scan, run_security_scan.
Choose Vulnicheck when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
check_package_vulnerabilities, scan_dependencies, scan_installed_packages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | BLACKDUCK_MCP_GATEWAY_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 2 | 10 |
| Full listing | View Black Duck Security Scanner | View Vulnicheck |
Tools & capabilities
Black Duck Security Scanner tools 2
run_changes_security_scan• **Faster**: Analyzes only changed code<br>• **Focused**: Shows issues from your changes<br>• **Iterative**: Perfect for dev workflows & CI/CD<br>• **Efficient**: Reduces scan cost and timerun_security_scan• Analyzing specific files/directories<br>• Focused security review of critical paths<br>• Quick checks during development<br>• Non-git projects
Vulnicheck tools 10
check_package_vulnerabilitiesCheck a specific Python package for vulnerabilitiesscan_dependenciesScan dependency files (requirements.txt, pyproject.toml, etc.)scan_installed_packagesScan currently installed Python packagesget_cve_detailsGet detailed information about a specific CVEscan_for_secretsDetect exposed secrets and credentials in codescan_dockerfileAnalyze Dockerfiles for vulnerable Python dependenciesscan_github_repoComprehensive security scan of GitHub repositoriesassess_operation_safetyAI-powered risk assessment for operationsvalidate_mcp_securityValidate MCP server security configurationscomprehensive_security_checkInteractive AI-powered security assessment
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Black Duck Security Scanner
{
"mcpServers": {
"black-duck-security-scanner": {
"command": "npx",
"args": [
"-y",
"@black-duck/mcp-server"
],
"env": {
"BLACKDUCK_MCP_GATEWAY_KEY": "YOUR_BLACKDUCK_MCP_GATEWAY_KEY_HERE"
}
}
}
}
Vulnicheck
{
"mcpServers": {
"vulnicheck": {
"url": "http://localhost:3000/mcp"
}
}
}
Frequently asked questions
Black Duck Security Scanner is categorized under Security and uses a local stdio subprocess. Vulnicheck belongs to Security and uses a remote HTTP/SSE transport. Pick Black Duck Security Scanner for security work and Vulnicheck for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Black Duck Security Scanner has no declared pricing — check the project's own site. Vulnicheck has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add black-duck-security-scanner and vulnicheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Black Duck Security Scanner has a quality signal of 53/100 (Good) with 0 views, 0 installs and 1 GitHub stars. Vulnicheck has 49/100 (Fair) with 3 views, 0 installs and 11 GitHub stars.