service-test-mcp
Related Servers
Alternatives to service-test-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to test WCF/SOAP and REST services directly, with WSDL discovery, authenticated calls, and deterministic assertions. Supports YAML multi-step scenarios with variable extraction, JSONPath/JSON Schema checks, and CI runs without spawning PowerShell or curl.12MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to author, validate, and execute browser/API test plans with parallel drivers, assertions, and captured evidence such as screenshots and network logs.1MIT
- AlicenseNot gradedqualityCmaintenanceIt enables AI agents to connect to a live Chrome browser for automation and authorized security testing, including session-aware tab control, network capture and replay, DOM inspection, screenshots, and background workflows.MIT
- AlicenseNot gradedqualityBmaintenanceThis server enables unified testing of web, Electron, and Windows desktop applications by connecting AI clients to application controls. It supports creating requirement-traced test plans, executing automated suites, and generating evidence-rich, auditable reports.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered web test automation with self-healing locators and automatic GitHub checkin.-
- AlicenseBqualityCmaintenanceEnables QA/SDET engineers to test APIs by ingesting Swagger/OpenAPI specs and Postman collections, generating and executing tests in multiple languages and frameworks with real-time progress tracking.1151 npm41 PyPI6MIT
TDQS
Scored across 17 tools
Tools are mostly distinct by resource and action, with clear separation between discovery (list/describe/check), calls, sessions, and scenario execution. The only mild overlap is among soap_call, rest_call, and call_operation, which all execute requests but target different service modes; descriptions clarify the choice.
All names use snake_case and most are verb-first (list_, describe_, check_, run_, validate_, import_, reload_, end_). A few deviate in form—soap_call, rest_call, session_variables—but remain readable and predictable.
17 tools is slightly above the typical 3–15 range, but the domain spans service discovery, connectivity, direct/profile calls, session management, traffic import, and scenario/suite execution. Each tool maps to a distinct test-automation capability, so the count is reasonable.
The surface covers the main test lifecycle: service/operation discovery, connectivity, SOAP/REST/profile calls, session and test-customer management, assertions, traffic-log import, and scenario validation/execution/suite runs. Minor gaps exist around explicit scenario file management (listing/reading/editing) and manual scenario creation, but these are largely external YAML workflows.