CodeInspectus
Related Servers
Alternatives to CodeInspectus
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenancePredeploy security scanner for AI-generated code. 80+ vulnerability patterns across secrets, auth, injection, config, Supabase, and logging. Runs locally, code never leaves your machine. Optional x402 witnessed attestation.94 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceLocal-first security check for AI coding agents — finds hardcoded secrets, exposed .env files, git-history leaks and vulnerable dependencies (OSV), entirely on your machine. Ask your agent "is this safe to ship?" and get a Launch Readiness score with a fix for every finding.MIT
- AlicenseAqualityBmaintenanceStatic security scanner for AI-generated (vibe-coded) Supabase and Next.js apps. Runs as an MCP server so an LLM can scan, explain findings, and produce fixes while it writes code, all locally and offline.566 npmMIT

AppLedgerofficial
AlicenseAqualityBmaintenanceSecurity checks for apps built with AI: Trivy and Opengrep findings explained in plain English, with a fix request for your coding agent. Hosted scan by default (only files Git would commit, never secret files) or fully local.542 PyPIMIT- AlicenseBqualityBmaintenanceSecurity MCP server with 300+ rules for AI-generated code. Scans Next.js, Supabase, Clerk, Stripe, Prisma, Hono, GraphQL and 20+ modules. Zero config, runs locally.391,641 npm6Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAutomatically detects security vulnerabilities in AI-generated code, scanning for hardcoded secrets, injection flaws, XSS, weak cryptography, authentication issues, path traversal, and vulnerable dependencies across JavaScript, Python, Java, and Go.14 npm2MIT
TDQS
Scored across 10 tools
Each tool targets a distinct phase of the workflow: scanning (scan/rescan), reporting (compliance_report, explain_finding, generate_sbom), inspection (list_rules, setup), and cleanup lifecycle (plan/apply/rollback). The main overlap is between setup and list_rules, both surfacing engine/DB versions and health, which could cause occasional misselection. Otherwise boundaries are clear.
All tools share the codeinspectus_ prefix and most follow a verb_noun pattern (explain_finding, generate_sbom, plan_cleanup, apply_cleanup, rollback_cleanup, compliance_report). Minor deviation: scan, setup, and rescan are bare verbs/single words rather than verb_noun, but the convention is still readable and predictable overall.
Ten tools is well-scoped for a security scanner with scanning, reporting, engine management, and a guarded cleanup lifecycle. Each tool earns its place with no obviously redundant entries.
The surface covers the full workflow: scan, rescan/diff, finding explanation, compliance mapping, SBOM generation, engine setup, and a safe plan/apply/rollback cleanup cycle. Minor gaps exist around scan-history management (no explicit list/delete of prior scans) and configuration of scan options beyond what scan accepts, but agents can work around these via scan_id references.