qa-toolkit-mcp
Related Servers
Alternatives to qa-toolkit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceRead-only server that reports what is actually true in a local Ansible checkout: the option specs of installed modules, task-argument validity checks, role interfaces, redacted inventory, play structure, effective config, requirements drift, and which tasks a collection upgrade would break. It lets coding agents verify specs and arguments against the installed collections before writing anything, without running plays, connecting to managed hosts, or supplying vault secrets.11542 npm1MIT
- AlicenseAqualityAmaintenanceocal-first, read-only MCP server that audits repository test architecture across ten language ecosystems. It returns deterministic evidence-backed findings, blockers, rankings, and repository-native test plans without modifying source files.20601 npmMIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for Markdown, MDX, and OpenAPI docs, exposing list, search, fetch, and OpenAPI spec tools over stdio.1MIT
- AlicenseAqualityDmaintenanceA stdio MCP server that caches Swagger/OpenAPI documents for multiple backend services and provides offline API search, retrieval, and request example generation. It only contacts remote servers when explicitly refreshing the cache.115 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, read-only static inspection of Python/FastAPI, Docker, and GitHub Actions release evidence through a stdio interface, returning rule and instance findings without importing or executing target code.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes 11 agent-native QA tools over stdio so coding agents can discover a project, analyze risk, select the smallest relevant test set, generate and dry-run tests, triage failures, propose tiered heals, analyze flakes, generate quality reports, and evaluate release readiness. Planning and healing tools stay read-only or propose-only, while execution defaults to dry-run, keeping agent actions safe and evidence-backed.MIT
TDQS
Scored across 4 tools
Each tool has a distinct role in the QA workflow: capabilities reporting, API surface discovery, case compilation, and reference auditing. There is no meaningful overlap that would cause misselection.
Three tools follow a clear qa_verb_noun pattern (qa_discover_api_surface, qa_compile_indexed_cases, qa_audit_case_references). qa_capabilities is a minor deviation as a noun-only tool, but it remains readable and consistent enough.
Four tools is well-scoped for a narrow QA toolkit focused on OpenAPI questionnaire discovery, compilation, and auditing. Each tool appears to earn its place without excess.
The set covers a discovery-to-compilation-to-audit flow, but it lacks obvious lifecycle operations such as listing or retrieving compiled cases and updating/deleting indexed cases. These gaps may force agents to work around the surface when managing cases.