# k11 API Contract QA (pypi · k11-api-contract-qa-mcp)

Which services an API change breaks and why: OpenAPI, GraphQL, gRPC, AsyncAPI, SOAP.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `k11-api-contract-qa-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp.md), [page](https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp)

## Channel facts

- Registry: `pypi`
- Package: `k11-api-contract-qa-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 30 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to K11-Software-Solutions/k11techlab-api-contract-qa-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 861 tokens (~107/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the k11 API Contract QA MCP server?

k11 API Contract QA runs locally as a PyPI package, launched with uvx k11-api-contract-qa-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add k11-software-solutions-api-contract-qa -- uvx k11-api-contract-qa-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "k11-software-solutions-api-contract-qa": {
      "command": "uvx",
      "args": [
        "k11-api-contract-qa-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "k11-software-solutions-api-contract-qa": {
      "command": "uvx",
      "args": [
        "k11-api-contract-qa-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add k11-software-solutions-api-contract-qa -- uvx k11-api-contract-qa-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "k11-software-solutions-api-contract-qa": {
      "type": "local",
      "command": [
        "uvx",
        "k11-api-contract-qa-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add k11-software-solutions-api-contract-qa --command uvx --arg k11-api-contract-qa-mcp
```

### Hermes

```yaml
mcp_servers:
  k11-software-solutions-api-contract-qa:
    command: "uvx"
    args: ["k11-api-contract-qa-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "k11-software-solutions-api-contract-qa": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "k11-api-contract-qa-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add k11-software-solutions-api-contract-qa -t stdio -c uvx -a k11-api-contract-qa-mcp
```

### Other

```json
{
  "mcpServers": {
    "k11-software-solutions-api-contract-qa": {
      "command": "uvx",
      "args": [
        "k11-api-contract-qa-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 80, +19)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.27

### 2026-11-20 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 61, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-14 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-13 (score 61)

First indexed and scored.

## MCP tools (8)

### `list_operations` (~58 tokens)

List operations

List the operations in a contract (OpenAPI, Swagger, GraphQL, .proto, AsyncAPI or WSDL; a project path or
\<git-ref>:<path>). Also tells you the detected format.

Input parameters:

- `spec` (string, required)

### `diff_contracts` (~86 tokens)

Diff contracts

Compare two versions of a contract (any supported format) and classify every change as breaking or
compatible, with the rule, field path, before/after and severity.
Example: base_spec='origin/main:openapi.yaml', head_spec='openapi.yaml'.

Input parameters:

- `base_spec` (string, required)
- `breaking_only` (boolean)
- `head_spec` (string, required)

### `assess_impact` (~103 tokens)

Assess impact on consumers

Which known consumers a spec change breaks, and why (field-level when consumers list the fields they
read/send). Verdict: breaking | breaking_no_known_consumers | compatible; needs_human when 2+ consumers or a
high-criticality consumer break. Consumers come from .qa-mcp/consumers.yaml.

Input parameters:

- `base_spec` (string, required)
- `consumers_file`
- `head_spec` (string, required)
- `write_report` (boolean)

### `discover_consumer_usage` (~91 tokens)

Discover consumer usage

Scan a consumer service's source code (inside the project) for calls to the provider, with file and line
as evidence, and draft its consumers.yaml entry. HTTP paths, GraphQL query documents (exact fields read),
gRPC stub calls, SOAP client calls, and AsyncAPI topic names.

Input parameters:

- `consumer_dir` (string, required)
- `consumer_name`
- `spec` (string, required)

### `check_live_conformance` (~104 tokens)

Check live conformance

Call a running endpoint (e.g. endpoint='GET /orders/{id}', path_params={'id': '1001'}) and check status,
content type and the JSON body against the spec's response schema. Header values may use ${ENV:NAME}.

Input parameters:

- `base_url` (string, required)
- `body`
- `endpoint` (string, required)
- `headers`
- `path_params`
- `query`
- `spec` (string, required)

### `check_deployed_contract` (~120 tokens)

Check deployed contract

Compare what a running service publishes with the spec file: GraphQL introspection (url = the GraphQL
endpoint), a WSDL URL (e.g. http://host/orders?wsdl), or a published OpenAPI/Swagger/AsyncAPI document
(e.g. http://host/v3/api-docs). Verdict: matches | drift | incompatible. gRPC is not supported (needs
reflection). Header values may use ${ENV:NAME}.

Input parameters:

- `headers`
- `spec` (string, required)
- `url` (string, required)

### `generate_api_tests` (~77 tokens)

Generate API tests

Generate contract tests (status + JSON schema) for some or all endpoints: pytest + httpx, or Java REST
Assured (JUnit 5). Returns the files; write them with write_test.

Input parameters:

- `endpoints`
- `framework` (string)
- `java_package` (string)
- `spec` (string, required)

### `write_test` (~48 tokens)

Write test file

Write a generated file under tests/ or src/test/ only. Won't overwrite unless asked.

Input parameters:

- `content` (string, required)
- `overwrite` (boolean)
- `path` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 61
- 2026-11-19: 76
- 2026-11-18: 61
- 2026-11-17: 61
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 61

## Common questions

### What is the k11 API Contract QA MCP server?

k11 API Contract QA is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/api-contract-qa. Which services an API change breaks and why: OpenAPI, GraphQL, gRPC, AsyncAPI, SOAP. This page covers its PyPI package (k11-api-contract-qa-mcp).

### Is the k11 API Contract QA MCP server safe to use?

k11 API Contract QA scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the k11 API Contract QA MCP server expose?

k11 API Contract QA exposes 8 tools: list_operations, diff_contracts, assess_impact, discover_consumer_usage, check_live_conformance, and 3 more. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.

### Is the k11 API Contract QA MCP server still maintained?

k11 API Contract QA is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the k11 API Contract QA MCP server under?

k11 API Contract QA declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the k11 API Contract QA MCP server?

VerifyMCP ran 15 checks on k11 API Contract QA, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about k11 API Contract QA: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/k11-api-contract-qa-mcp/
- Socket report: https://socket.dev/pypi/package/k11-api-contract-qa-mcp
- Repository: https://github.com/K11-Software-Solutions/k11techlab-api-contract-qa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp.json
- HTML version of this page: https://verifymcp.io/servers/k11-software-solutions-api-contract-qa/k11-api-contract-qa-mcp
