A
licenseA
qualityB
maintenanceMCP server that generates ISO/IEC/IEEE 29119-3 compliant test plan drafts from project information, providing a structured resource for the standard's test plan outline and a tool for draft creation.
1
106 npm
MIT
Test assistent MCP server
Related Servers
Alternatives to Test assistent MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that automates Playwright-based UI and API testing, supporting test case generation from requirements or API specs, and execution with detailed reports.3 npm1MIT
- FlicenseNot gradedqualityDmaintenanceThis MCP server provides a tool to generate manual test cases in Markdown or CSV format from documentation files and custom rules. It supports text and PDF inputs and can leverage LLM sampling to automate the creation of detailed test scenarios.-
- FlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to programmatically run tests, query results, and receive intelligent recommendations about test execution strategy.-
- AlicenseBqualityBmaintenanceAn MCP server for TestRail that prepares everything needed to generate test cases from Jira tickets, Confluence pages, or free-form specs and pushes them back to TestRail.3122 PyPI2MIT
- AlicenseCqualityCmaintenanceMCP server for TestNeo quality workflows, enabling test generation, execution, and analysis through MCP-compatible IDE clients.4811 npmGPL 3.0
TDQS
A3.6/5.0
Scored across 6 tools
Disambiguation4/5
generate_test_cases and generate_test_data are the most confusable pair, but their descriptions explicitly delineate them (technique-driven cases vs raw values). The catalog_* pair and the advise/checklist pair are distinct in purpose, though advise_technique and checklist_for both operate on a described context, which creates mild overlap.
Naming Consistency4/5
Five of six tools follow a clean verb_noun pattern (generate_test_cases, generate_test_data, advise_technique, catalog_heuristics, catalog_techniques). checklist_for breaks the pattern with a noun+preposition form, but it is still readable and clearly named.
Tool Count5/5
Six tools is well within the ideal 3-15 range and each has a clear, non-redundant role in the testing workflow. No tool feels padded or superfluous.
Completeness4/5
The surface covers generation (cases and data), technique/heuristic catalogs, advisory, and checklists, forming a coherent lifecycle for a test-assistant domain. Minor gaps exist (e.g., no export/format or test-execution helper), but agents can work around them.
Maintenance
ActivityMaintained
ResponsivenessNo issues