Skip to main content
Glama
rog0x

mcp-testing-tools

by rog0x

Related Servers

Alternatives to mcp-testing-tools

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to programmatically inspect, test, and validate other MCP servers by exposing MCP Workbench capabilities as structured tools. It supports automated test spec generation, execution, and detailed failure analysis to ensure server reliability.
      4
      7 npm
      Apache 2.0
    • 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
      A
      quality
      A
      maintenance
      A specialized testing harness that enables AI assistants to thoroughly test other MCP servers by connecting to them, discovering their tools/resources/prompts, executing test calls, and performing end-to-end validation with LLM integration.
      14
      4
      MIT
    • 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.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but generate_tests and generate_assertions overlap slightly since generated test cases often include assertions. generate_mock_data and generate_api_mock are similarly related, though the former is general-purpose data and the latter is schema-driven API responses.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: generate_tests, generate_mock_data, generate_api_mock, generate_assertions, and analyze_test_coverage. The naming convention is uniform and predictable.

    Tool Count5/5

    Five tools is a well-scoped set for a testing-focused server. Each tool covers a distinct aspect of test generation, mocking, assertions, or coverage analysis without unnecessary redundancy.

    Completeness4/5

    The tool surface covers test generation, mock data, API mocking, assertions, and coverage analysis well. Minor gaps exist, such as no direct test execution or test file management, but the core testing workflow is addressed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues