Skip to main content
Glama
gabriel-tbc

qa-toolkit-mcp

by gabriel-tbc

Related Servers

Alternatives to qa-toolkit-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that performs mutation testing and diff scoping to score how trustworthy tests are for detecting regressions in changed code.
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      MCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.
      10
      -
    • F
      license
      A
      quality
      C
      maintenance
      MCP server for FSM report migration analysis, providing fuzzy search of report mappings, pattern registry, and columnar report generation.
      7
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables automated maintenance and code analysis for Python/pytest repositories in isolated Docker environments. It supports read-only investigations, fix-and-verify tasks, and provides full audit trails with SQLite event history and artifact exports.
      MIT

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: listing runs, getting a single run's details, and comparing two runs. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow the consistent pattern 'qa_<verb>_runs' (list_runs, get_run, compare_runs), using snake_case and a clear verb_noun structure.

    Tool Count4/5

    Three tools is on the lower end but still reasonable for a focused test run analysis toolkit. The count matches the scope of listing, retrieving, and comparing runs.

    Completeness3/5

    The set covers the core operations of browsing and comparing test runs, but it lacks tools for creating, updating, or deleting runs, and flakiness detection is explicitly omitted. There are notable gaps for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues