Skip to main content
Glama

Related Servers

Alternatives to LeanGate

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to scan GitHub repositories for security vulnerabilities, deployment blockers, and code quality issues. It provides detailed findings and auto-generated code patches to help developers ensure their code is production-ready.
      31 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      It lets clients request design-time audits of Python and TypeScript agent applications for defects such as unbounded loops, ungated destructive actions, weak argument validation, insufficient run budgets, absent resiliency controls, overlooked evals, and poor observability. Findings include supporting evidence and feed an approval-driven mechanism for reviewing proposed fixes without mutating the original source.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to enforce UI/UX best practices and backend performance auditing, providing design guidelines, compliance checks, component search, and performance optimizations to eliminate generic or sloppy code.
      7
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to submit work for external review before declaring a task done, receiving evidence-backed fix lists and verdicts based on git-measured changes and calibrated quality scoring.
      3
      MIT

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct action in the code-quality workflow: feedback capture, report viewing, pre-write reuse search, post-change gate, minimization, equivalence proof, and dependency vetting. The potential overlap between check_reuse and check_dependency is resolved by scope (functions vs packages), and minimize/prove_equivalent differ clearly in intent and return value. An agent can select the right tool from the descriptions alone.

    Naming Consistency4/5

    All names use snake_case, and six of seven follow a verb_noun/verb_object pattern (record_feedback, show_report, check_reuse, verify_lean, prove_equivalent, check_dependency). The lone single-verb name (minimize) is a minor deviation but still clear and consistent in style. No mixed casing or vague verbs.

    Tool Count5/5

    Seven tools is well-scoped for a quality-gate server, covering the full loop from writing code to verifying, minimizing, and dependency checking. Each tool has a clear job and no obvious redundancy. Not too few, not bloated.

    Completeness4/5

    The surface covers the core lifecycle: pre-write reuse/dependency checks, post-change verification, minimization with testing, equivalence proof, feedback, and dashboard reporting. Gaps are minor—there is no tool to list past findings programmatically, and security waivers are intentionally CLI/human-only—but agents can work around these. Overall a complete set for the stated purpose.