No user-submitted related servers found.
Scored across 309 tools
The set aggregates multiple overlapping test-management domains: qmetry_* and qtm4j_* both expose near-identical concepts (test cases, cycles, requirements, issues) with different tool names, and within each product there are many closely related fetchers (e.g., qmetry_fetch_test_case_details, qmetry_fetch_test_cases, qmetry_fetch_test_case_steps, qmetry_fetch_test_case_steps_with_udf, qmetry_fetch_test_case_executions). An agent can easily pick the wrong fetch/update variant or the wrong product's equivalent tool.
Almost all tools follow a predictable product-prefix + verb_noun snake_case pattern (qmetry_create_test_case, bugsnag_list_project_errors, zephyr_update_test_case, swagger_get_api_definition). Minor deviations exist: the 'contract-testing_' prefix uses a hyphen rather than an underscore, and a few QMetry tools redundantly repeat the product (qmetry_fetch_qmetry_list_projects).
At 309 tools this is far beyond any reasonable scope, spanning nine distinct products with heavy duplication (many Bi-Directional Contract Testing fetchers, extensive admin/CRUD sets per product). This is the definition of an extreme count mismatch.
Breadth is enormous and each product area appears to have fairly full CRUD/lifecycle coverage (create/update/delete for test cases, cycles, suites, issues, requirements, webhooks, secrets, portals, etc.). Some aggregations still look partial (e.g., Zephyr has no delete tools surfaced), so minor gaps remain, but the surface is largely complete.