k11 API Contract QA
PYPI · K11-API-CONTRACT-QA-MCP
Which services an API change breaks and why: OpenAPI, GraphQL, gRPC, AsyncAPI, SOAP.
Available components
Last scanned (15 hours ago)
Scores higher than 78% of PyPI servers
Category Testing and QA
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to K11-Software-Solutions/k11techlab-api-contract-qa-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 861 tokens (~107/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +19
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.27 ▲ functional
- 20 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/k11-api-contract-qa-mcp@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | K11-Software-Solutions/k11techlab-api-contract-qa-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/K11-Software-Solutions/k11techlab-api-contract-qa-mcp/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3855231810 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:aae4f8b28f4d63a568cb13e90d27d3a690ff73bbca36c64915443d13297f3606 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_impact Assess impact on consumers ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| base_spec | string | yes | – |
| consumers_file | – | – | – |
| head_spec | string | yes | – |
| write_report | boolean | – | – |
No output schema declared.
No examples provided.
check_deployed_contract Check deployed contract ~120
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | – | – | – |
| spec | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
check_live_conformance Check live conformance ~104
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | yes | – |
| body | – | – | – |
| endpoint | string | yes | – |
| headers | – | – | – |
| path_params | – | – | – |
| query | – | – | – |
| spec | string | yes | – |
No output schema declared.
No examples provided.
diff_contracts Diff contracts ~86
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| base_spec | string | yes | – |
| breaking_only | boolean | – | – |
| head_spec | string | yes | – |
No output schema declared.
No examples provided.
discover_consumer_usage Discover consumer usage ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consumer_dir | string | yes | – |
| consumer_name | – | – | – |
| spec | string | yes | – |
No output schema declared.
No examples provided.
generate_api_tests Generate API tests ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | – | – | – |
| framework | string | – | – |
| java_package | string | – | – |
| spec | string | yes | – |
No output schema declared.
No examples provided.
list_operations List operations ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | string | yes | – |
No output schema declared.
No examples provided.
write_test Write test file ~48
Write a generated file under tests/ or src/test/ only. Won't overwrite unless asked.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| overwrite | boolean | – | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
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.
pypi · k11-api-contract-qa-mcp
claude mcp add k11-software-solutions-api-contract-qa -- uvx k11-api-contract-qa-mcp
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.