Skip to main content
Glama

Related Servers

Alternatives to MCP QA Lab

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A local-first, deterministic, read-only MCP server that audits test suites for false-green tests, tautological assertions, and mock-contract drift, ensuring tests truly validate production code. It provides tools to detect test fidelity issues, verify mock drift, and synthesize strict mock contracts.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.
      6
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that lets coding agents test AI agents. Create YAML test cases, snapshot golden baselines, check for regressions, and generate visual reports all from inside Claude Code or any MCP-compatible tool. Works with LangGraph, CrewAI, OpenAI, Claude, Mistral, and any HTTP API.
      10
      63 npm
      540 PyPI
      134
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP and coding-agent reliability harness that captures bounded, sanitized failure evidence and generates deterministic executable regression tests. Capture is opt-in; no API key or hosted service is required.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
      3
      GNU Lesser General Public v2.1 only

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (listing, registering, inspecting, checking, measuring, generating, executing, reporting). The only potential confusion is between run_static_checks and measure_context_cost, but their descriptions clarify that one focuses on quality/size analysis and the other on serialized metadata cost and duplicate descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_targets, register_target, inspect_target, run_static_checks, measure_context_cost, generate_scenarios, run_target_tool, build_report). The naming is uniform and predictable.

    Tool Count5/5

    Eight tools is an appropriate scope for a QA lab. The set covers the main workflow areas without being bloated or sparse, aligning well with the typical 3-15 tool sweet spot.

    Completeness4/5

    The toolset covers the core workflow: register, inspect, run checks, measure cost, generate scenarios, execute a tool, and build a report. A minor gap is the absence of a delete/unregister target operation, which could make target lifecycle management incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues