Skip to main content
Glama
Repo Test Architect

Repo Test Architect

Related Servers

Alternatives to Repo Test Architect

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A local-first MCP server that scores your codebase's Build Readiness by reading code and running tests on your machine, outputting a diligence-grade score and risk register without uploading your source.
      5
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      A secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server that scans a repository once and answers architecture questions from an evidence-backed graph, enabling dependency analysis, impact analysis, and codebase exploration without re-reading the source tree.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.
      4
      14 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 20 tools

    Disambiguation3/5

    There is a clear effort to distinguish tools via descriptions (e.g. review_repository vs analyze_repository bounded-vs-complete, single-project vs multi-project variants), but the surface contains many near-parallel families: audit_repo vs get_audit_graph vs audit_projects, and rank_test_candidates vs rank_project_candidates, etc. An agent must read carefully to select the right tool, and several boundaries (audit_repo/get_audit_graph in particular) remain genuinely fuzzy.

    Naming Consistency4/5

    Names are uniformly snake_case and overwhelmingly follow a verb_noun pattern (list_adapters, review_repository, generate_project_test_plan, analyze_test_placement). Minor deviations exist where a noun precedes a qualifier (get_audit_graph, explain_target), and the project_ infix is inconsistently applied as a scoping hint, but the overall convention is predictable.

    Tool Count3/5

    Twenty tools is on the heavy side for the domain, and much of the count comes from redundant project-level vs single-project variants of the same operations. The breadth is defensible given the layered workflow (detect, audit, review, rank, plan, explain), but it feels over-expanded rather than tightly scoped.

    Completeness4/5

    The lifecycle for a read-only test-architecture review is well covered: detection, audit, bounded and full analysis, summarization, ranking, planning, placement, stats, and execution hints. The one notable dead end is generate_selected_test, which is a structured stub that generates nothing, but the core analysis surface has no glaring gaps.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data