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.
      44 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
      103 npm
      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
      2,352 npm
      5
      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.
      19 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Static analysis for vibe-coded apps. Flags security, reliability, performance, and AI quality issues in code generated by Cursor, v0, Bolt, and Copilot.
      313 npm
      15
      MIT

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: full scan, rescan with diff, compliance reporting, single-finding explanation, SBOM generation, rule listing, and setup. Overlaps are minimal, and the descriptions clarify boundaries such as scan vs. rescan and compliance_report vs. scan.

    Naming Consistency4/5

    All names use the consistent codeinspectus_ prefix and snake_case, making them predictable. The set is mostly verb_noun, but scan/rescan/setup deviate slightly from a strict verb_noun pattern, which is a minor inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for an offline security inspection server. Each tool earns its place across setup, scanning, reporting, remediation explanation, and SBOM generation without bloat or thinness.

    Completeness4/5

    The surface covers the core lifecycle: engine setup, scan, rescan diff, finding explanation, compliance view, SBOM generation, and rule/database listing. A minor gap is the lack of an explicit tool to list or retrieve prior scans and their full findings beyond referencing finding IDs.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive