Skip to main content
Glama
RepoAssay

Repo Test Architect

by RepoAssay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Repo Test Architect

No user-submitted related servers found.

    Related Servers

    • Obra CTO

      lilycip
      A
      license
      A
      quality
      B
      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
      63 npm
      Apache 2.0

    • local-mcp-toolbox

      chriswayneh
      A
      license
      Not graded
      quality
      A
      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.
      MIT

    • Knossos MCP

      AraneaDev
      A
      license
      Not graded
      quality
      A
      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.
      3
      MIT

    • sdlc-integrity-mcp

      AsobaCloud
      A
      license
      A
      quality
      A
      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
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and descriptions explicitly guide when to use which (e.g., analyze_repository vs audit_repo vs audit_projects). Some overlap exists among tools that operate on the same project-audits/v1 artifact, but their scopes and usage notes are clearly differentiated.

    Naming Consistency4/5

    Tool names generally follow a verb_noun pattern with underscores (e.g., list_adapters, detect_projects, generate_test_plan). Minor deviations include using 'repo' instead of 'repository' (audit_repo vs analyze_repository) and inconsistency between 'project_test_plan' and 'test_plan', but the overall pattern is predictable.

    Tool Count3/5

    The server has 19 tools, which falls in the borderline heavy range. While each tool has a specific role, many are specialized subsets of the umbrella analyze_repository tool, making the count feel slightly inflated for the core purpose.

    Completeness4/5

    The tool set covers the major steps of repository analysis: detection, audit, summarization, ranking, planning, placement analysis, and execution hints. However, generate_selected_test is a deferred stub that does not actually generate test code, and there is no tool to modify detection rules or adapters, leaving some gaps in the full lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources