← Back to directory
C

CodeInspectus MCP Server

Community
Local-first MCP security scanner for AI-generated apps
GitHub source repository ↗
★ 37 Stars Category · Dev Tools Popular
75FMRS · B

An unusually disciplined local security scanner: SHA-pinned engines, zero scan-time egress, no telemetry, redacted secrets, a three-state honest evidence model, and rare candor about its own limits (narrow native rules, AI-drafted compliance mappings, heuristic prompt-injection detection). Well suited to agent-driven scan-fix-rescan security loops; not a substitute for deep audits, runtime testing, or compliance certification. MIT licensed, solo-maintained by Synvoya, with independent security review actively solicited.

Reliability
11/20
Security and permissions
18/20
Maintenance
13/20
Documentation
19/20
Setup experience
14/20
Read the FMRS scoring method →

CodeInspectus is a local-first, privacy-preserving MCP security scanner and CLI maintained by Synvoya. Any AI coding agent (Claude Code, Cursor, Codex, Windsurf, Cline, Aider) can invoke it to scan AI-generated / "vibe-coded" code for real vulnerabilities, map findings to code-level compliance-framework coverage, and drive a scan → fix → rescan loop — fully on your machine, no account, zero network egress at scan time. It orchestrates three OSS engines — Opengrep (SAST/OWASP Top 10), Gitleaks (secrets), and Trivy (dependency CVEs, IaC, SBOM) — plus first-party AI-code-specific checks (Supabase RLS / inverted authz, prompt-injection sinks, model tool arguments reaching shell sinks, client-writable user_metadata authorization, dangerous HTML rendering, Firebase public writes, GitHub Actions workflow risks, and more), shipping 88 curated detections normalized into a CWE-keyed schema. Engine binaries are SHA-pinned and signature-verified; there is no telemetry. Compliance mappings are code-level coverage only, never certification.

Tools

codeinspectus_scan
Full local scan of a path (engines + AI checks). Returns CWE-keyed findings, detected technologies, native-pack and Pub dependency coverage, remediations, framework tags, and three-state repository evidence for supported runtime controls.
codeinspectus_rescan
Re-scan after fixes; diffs against a prior scan producing resolved / remaining / introduced, with fresh technology and pack coverage.
codeinspectus_compliance_report
Per-framework code-level control coverage report (not certification).
codeinspectus_explain_finding
Deep explanation plus full remediation for a single finding.
codeinspectus_generate_sbom
Generate a CycloneDX/SPDX SBOM using Trivy plus native Pub inventory/fallback (written to a managed directory by default, or a path you choose).
codeinspectus_list_rules
List active detectors, native-pack inventory and rule ownership, engine versions, detection-DB provenance and freshness, and structured setup/repair state.

Setup

Prerequisites: Node.js ≥22 (Node 24 LTS recommended); cosign on PATH when Opengrep or Trivy binaries need installation (fail-closed verification; Gitleaks verifies by checksum and needs no cosign). Register once per machine with your client (e.g. Claude Code: claude mcp add- codeinspectus '{"command":"npx","args":["-y","codeinspectus"]}'; Cursor: add to mcp.; VS Code: code --add-mcp; Codex: codex mcp add or config.toml with tool_timeout_sec = 600 recommended). Then run npx codeinspectus repair-engines to install hash-verified engines and databases. Scans then perform zero network I/O. Re-verify binaries any time with npx codeinspectus verify-engines.

claude_desktop_config.json
{"mcpServers":{"codeinspectus":{"command":"npx","args":["-y","codeinspectus"]}}}

Fit and risk

Best for

  • Security-conscious developers building apps with AI agents like Claude Code, Cursor, or Codex
  • Individuals and small teams who want fully offline, local code scanning with no source upload
  • Teams mapping CWE-keyed findings to code-visible compliance controls

Not for

  • Teams seeking full compliance certification or runtime security proof (the tool explicitly does neither)
  • Deep audits requiring cross-file/whole-program dataflow or runtime mobile testing
  • Restricted environments that cannot run Node.js ≥22 or install cosign and engine binaries
  • Essential Eight assessments (only ~1 of 8 mitigations is code-evidenced)

Required permissions

  • Reads project source and repository files (read-only; never edits or deletes your code)
  • Stores engine data and scan history under ~/.codeinspectus
  • Optionally writes one SBOM file (managed directory by default, or a chosen path)
  • Runs SHA-verified Opengrep/Gitleaks/Trivy binaries as local subprocesses
  • Reads git state for a git-safety recommendation; git operations require user approval and the tool never runs them itself

Risks and side effects

  • Prompt-injection detection is heuristic and immature; findings are worded "potential …" at medium confidence
  • Fixes are applied by your AI agent and need human review; the tool only reports and never edits code
  • Native rule coverage is deliberately narrow (mostly intrafile analysis); do not infer broader coverage than executed packs report
  • Compliance mappings are AI-drafted and maintainer-reviewed with 0 of 96 community-verified — not an audit
  • Engine binaries carry supply-chain risk, mitigated via SHA pinning, though setup/repair still downloads over the network

Troubleshooting

  1. Scan returns engine_setup other than ready: have the agent explain the state (repair_required / db_refresh_recommended / unsupported_platform) and, with approval, run npx codeinspectus repair-engines
  2. CVE rescan tracking not enabled: for a Trivy DB installed before 0.3.2, run repair-engines once to re-fetch via the verified path
  3. Client timeouts (especially Codex): set tool_timeout_sec to 600, since large-repository scans can exceed the default 60 seconds
  4. Native pack did not run: check pack_coverage and detected_technologies — each pack requires exact framework/dependency evidence (e.g. Flutter, openai-php/client, async-openai)
  5. Verify binary integrity: npx codeinspectus verify-engines; unpinned or mismatched binaries are refused

Use cases

Scanning AI-generated / vibe-coded apps for real vulnerabilities before shipping
Agent-driven scan → fix → rescan security loops
Producing code-level control coverage reports for OWASP, NIST CSF, ISO 27001, SOC 2 and more
Generating local SBOMs (CycloneDX/SPDX) including Dart/Flutter pubspec.lock dependency inventory
CI/local baseline and history comparisons, sealed evidence bundles, and GitHub/Jira/Linear issue payload export

Supported clients

Claude CodeFull support
CursorFull support
VS CodeFull support
CodexFull support
WindsurfFull support
ClineFull support
AiderFull support