codeinspectus_explain_finding
Deep explanation + full remediation for one finding.
How to use it
codeinspectus_explain_finding is exposed by the Codeinspectus MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the codeinspectus_explain_finding tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
Install Codeinspectus
npx codeinspectus repair-enginesOther tools in Codeinspectus (5)
Per-framework code-level control coverage (not certification).
CycloneDX/SPDX SBOM using Trivy plus native Pub inventory/fallback (written to the managed dir by default, or a path you choose).
Active detectors, native-pack inventory/rule ownership, engine versions, detection-DB + Trivy/Pub DB provenance and freshness, and structured machine setup/repair state.
Re-scan after fixes; diffs vs a prior scan → resolved / remaining / introduced, with fresh technology and pack coverage.
Full local scan of a path (engines + AI checks). Returns CWE-keyed findings, detected technologies, exact native-pack and Pub dependency coverage, remediations, framework tags, and three-state repository evidence for supported runtime controls.