Blackduck Polaris (npm) MCP Server
blackduck-polaris-mcp-server
npm
v0.3.1
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 2.1 = 98. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
2. Client adoption risk — 98 − 8 = 90. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −5 | publisher verification (unlocatable) — no provenance and no public repository to inspect |
| ✓ | inspection depth (source) — how much of the target the scan could see |
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 2
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([polaris_download_report]) co-exist with external-action tools ([polaris_create_issue_policy]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [polaris_download_report] → sinks [polaris_create_issue_policy]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow polaris_download_report → polaris_create_issue_policy
low Package has no source repositoryMTC-SUP-011
"blackduck-polaris-mcp-server" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package blackduck-polaris-mcp-server
Tools 67
Show each tool and what it can reach · statically extracted from the published source
polaris_create_issue_policynetwork egresspolaris_download_reportingests untrusted inputpolaris_assign_policyno sensitive capabilitypolaris_bulk_import_reposno sensitive capabilitypolaris_cancel_testno sensitive capabilitypolaris_create_api_tokenno sensitive capabilitypolaris_create_applicationno sensitive capabilitypolaris_create_bugtracker_configno sensitive capabilitypolaris_create_groupno sensitive capabilitypolaris_create_projectno sensitive capabilitypolaris_create_scheduling_policyno sensitive capabilitypolaris_create_service_account_tokenno sensitive capabilitypolaris_create_test_artifactno sensitive capabilitypolaris_create_userno sensitive capabilitypolaris_delete_applicationno sensitive capabilitypolaris_delete_issue_policyno sensitive capabilitypolaris_delete_reportno sensitive capabilitypolaris_export_audit_logsno sensitive capabilitypolaris_export_issues_to_trackerno sensitive capabilitypolaris_generate_reportno sensitive capabilitypolaris_get_audit_logsno sensitive capabilitypolaris_get_current_userno sensitive capabilitypolaris_get_detection_historyno sensitive capabilitypolaris_get_issueno sensitive capabilitypolaris_get_issue_countsno sensitive capabilitypolaris_get_notification_preferencesno sensitive capabilitypolaris_get_notification_subscriptionsno sensitive capabilitypolaris_get_occurrence_snippetno sensitive capabilitypolaris_get_remediationno sensitive capabilitypolaris_get_repono sensitive capabilitypolaris_get_report_statusno sensitive capabilitypolaris_get_testno sensitive capabilitypolaris_get_test_commentsno sensitive capabilitypolaris_get_test_metricsno sensitive capabilitypolaris_get_triage_historyno sensitive capabilitypolaris_get_userno sensitive capabilitypolaris_list_applicationsno sensitive capabilitypolaris_list_audit_categoriesno sensitive capabilitypolaris_list_branchesno sensitive capabilitypolaris_list_bugtracker_configsno sensitive capabilitypolaris_list_entitlementsno sensitive capabilitypolaris_list_groupsno sensitive capabilitypolaris_list_issue_policiesno sensitive capabilitypolaris_list_issuesno sensitive capabilitypolaris_list_occurrencesno sensitive capabilitypolaris_list_portfoliosno sensitive capabilitypolaris_list_projectsno sensitive capabilitypolaris_list_repo_branchesno sensitive capabilitypolaris_list_report_typesno sensitive capabilitypolaris_list_reportsno sensitive capabilitypolaris_list_reposno sensitive capabilitypolaris_list_scheduling_policiesno sensitive capabilitypolaris_list_scm_providersno sensitive capabilitypolaris_list_test_artifactsno sensitive capabilitypolaris_list_testsno sensitive capabilitypolaris_list_usersno sensitive capabilitypolaris_submit_remediation_feedbackno sensitive capabilitypolaris_test_jira_connectionno sensitive capabilitypolaris_test_repo_connectionno sensitive capabilitypolaris_triage_issueno sensitive capabilitypolaris_trigger_scanno sensitive capabilitypolaris_update_applicationno sensitive capabilitypolaris_update_bugtracker_configno sensitive capabilitypolaris_update_issue_policyno sensitive capabilitypolaris_update_notification_preferencesno sensitive capabilitypolaris_update_repono sensitive capabilitypolaris_update_userno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (67 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.3.1 latest |
A 90/100 | 2 | 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.
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 blackduck-polaris-mcp-server --onlineOther implementations of Blackduck Polaris 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Agent MCP server.