mcp-testing-tools
Related Servers
Alternatives to mcp-testing-tools
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides 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.-
- AlicenseAqualityCmaintenanceEnables 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.47 npmApache 2.0
- AlicenseAqualityAmaintenanceMCP 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.1063 npm540 PyPI134Apache 2.0
- AlicenseAqualityAmaintenanceA 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.144MIT
- FlicenseNot gradedqualityDmaintenanceAll-in-one automation platform for AI agents, providing browser automation, API testing, debugging, and testing tools via the MCP protocol.3-
- AlicenseNot gradedqualityBmaintenanceA 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.3GNU Lesser General Public v2.1 only
TDQS
Scored across 5 tools
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.
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.
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.
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.