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.
      51 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
      A
      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
      28 npm
      MIT
    • A
      license
      Not graded
      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.
      MIT
    • A
      license
      B
      quality
      A
      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,430 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.
      12 npm
      2
      MIT

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scan/rescan differ by diff-vs-fresh, cleanup tools form a plan/apply/rollback lifecycle, and the remaining tools target specific outputs (SBOM, compliance, explanation, rules, setup). No two tools overlap in a way that would cause misselection.

    Naming Consistency4/5

    All names use snake_case with a consistent codeinspectus_ prefix, which is predictable. Minor deviation from a pure verb_noun pattern in compliance_report and setup, but still readable and cohesive.

    Tool Count5/5

    Ten tools is well-scoped for a security scanning and remediation suite. Each tool earns its place: core scanning, diffing, cleanup lifecycle, SBOM generation, compliance mapping, explanation, rules inspection, and setup.

    Completeness4/5

    The surface covers the main scan-fix-rescan-cleanup workflow plus SBOM and compliance outputs. Minor gaps exist, such as no explicit tool to list or retrieve past scan metadata beyond rescan diffs, but agents can work around this.

    Maintenance

    ActivityActive
    ResponsivenessResponsive