
Which services an API change breaks and why: OpenAPI, GraphQL, gRPC, AsyncAPI, SOAP.
Public tool metadata for what this MCP can expose to an agent.
list_operationsLists a contract's operations and its detected format.Lists a contract's operations and its detected format.
No parameter schema in public metadata yet.
diff_contractsClassifies every change between two versions of a contract: rule, field path, before/after, severity.Classifies every change between two versions of a contract: rule, field path, before/after, severity.
No parameter schema in public metadata yet.
assess_impactWhich consumers a change breaks and why; the verdict and whether a person should decide. Optionally writes the report.Which consumers a change breaks and why; the verdict and whether a person should decide. Optionally writes the report.
No parameter schema in public metadata yet.
discover_consumer_usageFinds a consumer's calls to your API in its source code and drafts its consumers.yaml entry.Finds a consumer's calls to your API in its source code and drafts its consumers.yaml entry.
No parameter schema in public metadata yet.
check_deployed_contractCompares what a running service publishes with the spec: matches, drift or incompatible.Compares what a running service publishes with the spec: matches, drift or incompatible.
No parameter schema in public metadata yet.
check_live_conformanceCalls a running REST endpoint and checks the response against the spec. Header values can use ${ENV:NAME}.Calls a running REST endpoint and checks the response against the spec. Header values can use ${ENV:NAME}.
No parameter schema in public metadata yet.
generate_api_testsREST contract tests (status + JSON schema) for pytest + httpx or REST Assured.REST contract tests (status + JSON schema) for pytest + httpx or REST Assured.
No parameter schema in public metadata yet.
write_testWrites generated files under tests/ or src/test/ only, never overwriting unless asked.Writes generated files under tests/ or src/test/ only, never overwriting unless asked.
No parameter schema in public metadata yet.
Sponsors
QA_MCP_ROOTFolder of the service or repo with the spec (default: current directory)
Know which services an API change breaks before you merge it, and why. REST, GraphQL, gRPC, events and SOAP.
A pull request renames a field or tightens a request body. Its own tests pass. Three other services break in production. Spec-diff tools can tell you a change is "breaking", but not who it breaks, so teams either ignore the warnings or block every change. This MCP server answers the real question:
k11-api-contract-qa-mcp