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
      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
      48 npm
      Apache 2.0

    • local-mcp-toolbox

      chriswayneh
      A
      license
      A
      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.
      8
      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.
      2
      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
      5 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.6/5.0

    Scored across 19 tools

    Disambiguation3/5

    The set contains many overlapping artifact-consumption tools: analyze_repository subsumes several specialist outputs, and project-wide vs single-audit variants mirror each other. The long descriptions explicitly steer callers, but boundaries remain fuzzy enough that misselection is likely.

    Naming Consistency4/5

    Almost all tools use snake_case verb_noun naming, making the surface predictable. Minor deviations exist, such as audit_repo vs analyze_repository and project-qualified vs unqualified variants.

    Tool Count3/5

    19 tools is heavy for a repository test-architecture review server, and several tools only expose slices already included in analyze_repository. The specialized pipeline justifies some breadth, but the count is borderline excessive.

    Completeness3/5

    The analysis lifecycle is well covered: detection, auditing, ranking, planning, placement, stats, findings, and target explanation. However, actual test generation is explicitly deferred/non-functional and there is no write or execution surface, which is a notable gap for a test architect.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources