Skip to main content
Glama

Related Servers

Alternatives to CodeInspectus

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      F
      maintenance
      Predeploy 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 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-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
    • A
      license
      A
      quality
      B
      maintenance
      Static 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.
      5
      66 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Security 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.
      5
      42 PyPI
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Security 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.
      39
      1,641 npm
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Automatically 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 npm
      2
      MIT

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessLimited data