Skip to main content
Glama

Related Servers

Alternatives to codebase-doctor

No user-submitted related servers found.

    Related Servers

    • 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
      Local, deterministic review of Git changes for coding agents: weakened tests and CI gates, security-boundary changes, input-to-sink flows, and blast radius. Runs the RepoPilot Rust CLI over stdio; no source leaves the machine and no model is called.
      6
      294 npm
      24
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables read-only, evidence-led security audits of GitHub-hosted source code through explicit workflow primitives: repository reconnaissance, coverage-ledger planning, heuristic candidate leads, structured findings validation, independent verification gates, and JSON/Markdown report generation. It never clones, executes, or probes the target code, and marks runs incomplete until coverage and reviewer-verification gates pass.
      14
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Local code-graph engine for AI coding workflows: static analysis of Rust, Cangjie, ArkTS, TypeScript/JavaScript, C/C++, Python, and Shell projects into symbols, imports, call graphs, and quality gates, with pre-commit change review and impact analysis. Read-only by design — never executes build scripts or uploads code.
      6
      1
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding agents to perform evidence-based, read-only audits of supported software projects by exposing bounded project inventory and static-analysis findings for discovery, code review, integration tracing, security, and tests. Reports are returned as Markdown or JSON directly in the tool response, with no code executed or files written.
      8
      17 npm
      MIT

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct audit-lifecycle operations, and descriptions distinguish full audit, changed-scope review, repair verification, and intent verification. The main overlap is audit_codebase vs build_receipt, both of which run a read-only audit, though their outputs (full report vs coverage receipt) are sufficiently differentiated.

    Naming Consistency5/5

    All seven tool names follow a consistent snake_case verb_noun pattern. The verbs are varied but predictable, and there are no mixed conventions or naming collisions.

    Tool Count5/5

    Seven tools is well within the appropriate range for a focused audit/verification server. Each tool maps to a distinct operation in the audit lifecycle, and there is no apparent filler.

    Completeness4/5

    The surface covers auditing, receipt generation, changed-code review, repair verification, finding explanation, intent verification, and capability discovery. Minor gaps exist around dedicated finding enumeration/filtering and receipt comparison or verification, but agents can work around these using the existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues