Blackduck (raviraj87) MCP Server

@raviraj87/blackduck-mcp npm v1.1.0

Published by @raviraj87 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • blackduck_api_getno sensitive capability
  • blackduck_api_putno sensitive capability
  • blackduck_bulk_mark_reviewedno sensitive capability
  • blackduck_current_userno sensitive capability
  • blackduck_find_bad_mappingsno sensitive capability
  • blackduck_get_bom_component_filesno sensitive capability
  • blackduck_get_component_detailno sensitive capability
  • blackduck_get_component_originsno sensitive capability
  • blackduck_get_matched_filesno sensitive capability
  • blackduck_get_policy_violationsno sensitive capability
Show 20 more tools ↓
  • blackduck_get_project_versionsno sensitive capability
  • blackduck_get_snippet_matchesno sensitive capability
  • blackduck_get_version_policy_statusno sensitive capability
  • blackduck_get_vulnerabilitiesno sensitive capability
  • blackduck_get_vulnerability_summaryno sensitive capability
  • blackduck_healthno sensitive capability
  • blackduck_ignore_snippetno sensitive capability
  • blackduck_list_bom_componentsno sensitive capability
  • blackduck_list_componentsno sensitive capability
  • blackduck_list_project_componentsno sensitive capability
  • blackduck_list_projectsno sensitive capability
  • blackduck_list_scansno sensitive capability
  • blackduck_list_versionsno sensitive capability
  • blackduck_resolve_project_versionno sensitive capability
  • blackduck_search_cveno sensitive capability
  • blackduck_search_kb_componentno sensitive capability
  • blackduck_set_component_licenseno sensitive capability
  • blackduck_set_component_usageno sensitive capability
  • blackduck_set_component_versionno sensitive capability
  • blackduck_update_package_jsonno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 99/100 0 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/raviraj87-blackduck-mcp/badge.svg)](https://mcptrustchecker.com/registry/raviraj87-blackduck-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/raviraj87-blackduck-mcp"><img src="https://mcptrustchecker.com/registry/raviraj87-blackduck-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/raviraj87-blackduck-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @raviraj87/blackduck-mcp --online

Use the free API → How scoring works

Other implementations of Blackduck 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools