k11 Integration QA
OfficialRelated Servers
Alternatives to k11 Integration QA
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceFunctional API testing over MCP. Turns user stories into multi-step YAML test flows (chained calls, saved IDs, value and schema checks), adds read-only database checks that prove each change was stored, and generates negative and boundary tests from OpenAPI, including nested fields, where every bad input must get a 4xx and never a 5xx. Guardrails refuse writes on production-like environments, keep8MIT
- FlicenseNot gradedqualityDmaintenanceEnables spec-driven development acceptance gate with structured receipts, audit logs, and reviewer-ready evidence.-
- AlicenseNot gradedqualityCmaintenanceEnables running YAML-defined test suites against MCP servers and agent workflows, with live or simulated execution, assertions, and regression reporting.72 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceOrchestrates end-to-end testing of AI-powered incident remediation workflows through declarative YAML scenarios, fault injection, AI response evaluation, and automated command execution with comprehensive reporting.-
- 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 gradedqualityBmaintenanceGives AI coding agents dereferenced OpenAPI facts about the backend being implemented, and verifies that implementation against a local server via ping probes, single requests, contract tests, and ordered multi-step scenarios with extraction and assertions. It also spins up loopback mocks for missing dependencies and derives a relational data model from the spec, reconciling it with optional live database evidence and emitting additive SQL that is never executed.125 npmMIT
TDQS
Scored across 6 tools
Each tool maps to a distinct phase of the integration-QA workflow (read config, init config, validate a flow, run flows, watch a topic, fetch a report). The only real confusion is between integration_config and init_integration_config, which differ only by an 'init_' prefix, and get_report versus run_integration_tests, which both surface failing-step evidence.
Five of six tools use a clean snake_case verb_noun pattern (run_integration_tests, validate_flow, watch_topic, get_report, init_integration_config). integration_config breaks the pattern as a bare noun, but the deviation is minor and readable.
Six tools is well-scoped for a narrow integration-QA/Release-Gate domain, with no obvious filler. Each tool covers a distinct lifecycle step: configure, author, validate, observe, run, and report.
The surface covers the full loop from bootstrapping config through validating, running, inspecting, and reporting on flows. The main gap is that there is no way to update or edit an existing integration.yaml (only a one-shot init), forcing agents to rewrite the file blind.