QA Engineering MCP Hub
Related Servers
Alternatives to QA Engineering MCP Hub
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceKeyless, local MCP server bringing ISTQB / OWASP / IEEE / ISO / EU AI Act QA standards into your AI client. Standards-grounded retrieval, deterministic QA effort estimation, automated QA document quality review (0-100 rubric), and JUnit/CSV test-results flakiness analysis.6789 PyPI7Apache 2.0
- AlicenseAqualityDmaintenanceMCP server for running infrastructure health checks with TIBET provenance. It enables users to define, execute, and audit process health checks with dependency chaining and drift tracking.6MIT
- AlicenseAqualityAmaintenanceLocal-first production-readiness MCP server for AI-built apps. It runs read-only checks, produces an evidence-based readiness score, and guides fixes before launch.116Apache 2.0
- FlicenseNot gradedqualityDmaintenanceStarter scaffold for a workshop to build an MCP API testing server, intended to be extended through incremental steps.-
- FlicenseNot gradedqualityBmaintenanceLocal MCP server for static Python/TypeScript code audits, Playwright test generation, and SDLC health checks with a 0-100 quality score.-
- AlicenseAqualityDmaintenanceA local-first MCP server that scores your codebase's Build Readiness by reading code and running tests on your machine, outputting a diligence-grade score and risk register without uploading your source.522 npmApache 2.0
TDQS
Scored across 2 tools
hub_health (readiness/liveness) and hub_capabilities (feature inventory) are conceptually separable and the descriptions reinforce the split. They are still both metadata-only introspection calls, so an agent may occasionally grab one when it wanted the other.
Both tools use a clean, identical `hub_<noun>` snake_case pattern. There is no mixing of verbs, casing, or prefixes.
Two tools is very thin for something billed as a 'QA Engineering MCP Hub' — it is a stub surface rather than a scoped toolset. Both tools earn their place, but the count is far below what the stated purpose implies.
The surface covers only self-introspection; there are no QA-engineering operations at all (no test discovery, run, results, coverage, or reporting). An agent reaching for this hub for its advertised domain hits an immediate dead end.