k11 API Functional QA
PYPI · K11-API-FUNCTIONAL-QA-MCP
Functional API tests: story-to-flow, negative tests from the spec, DB checks, evidence.
Available components
Last scanned (18 hours ago)
Scores higher than 54% 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 Security50
- Malware scan not yet available for this package.Unverified
- 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 31 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-functional-qa-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 740 tokens (~92/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
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.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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.
- 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-functional-qa-mcp@0.1.1
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-functional-qa-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/K11-Software-Solutions/k11techlab-api-functional-qa-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3856657262 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:c255a31b570e8192f5f8794ceae45c89c6cd984582b97d404a71150bc9f3efb2 |
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 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
call_api Call API ~101
Make one request (e.g. call='GET /orders/{id}', path_params={'id': '1001'}) to explore an API while writing tests. Same guardrails as flows: writes only where allowed, secrets masked, schema checked when a spec is set.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | – | – | – |
| body | – | – | – |
| call | string | yes | – |
| environment | – | – | – |
| headers | – | – | – |
| path_params | – | – | – |
| query | – | – | – |
No output schema declared.
No examples provided.
draft_flow Draft flow from a user story ~58
Turn a user story or acceptance criteria into scenarios, the spec operations most likely involved, and a flow skeleton to complete (chain IDs with save/${...}, add value and db checks).
| Name | Type | Req | Description |
|---|---|---|---|
| spec | – | – | – |
| story | string | yes | – |
No output schema declared.
No examples provided.
export_pytest Export flow to pytest ~66
Turn a flow into a plain pytest + httpx test (database checks included), so the suite can live without this tool. Returns the code; with write=true saves it under tests/ (never overwriting).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| write | boolean | – | – |
No output schema declared.
No examples provided.
generate_negative_tests Generate negative tests ~151
Negative and boundary tests for one operation (e.g. 'POST /orders'), derived from the spec, including nested fields and array items: missing required fields, wrong types, values outside enums and min/max/length/item limits, missing parameters, no credentials, unknown IDs. Every case must get a 4xx, never a 5xx; boundary cases that must be accepted clean up after themselves. base_values supplies real values for the valid parts (e.g. {"customerId": "${fixture.customer.id}"}) with fixtures=["customer"]. Save the result with write_flow.
| Name | Type | Req | Description |
|---|---|---|---|
| base_values | – | – | – |
| endpoint | string | yes | – |
| fixtures | – | – | – |
| spec | – | – | – |
No output schema declared.
No examples provided.
list_environments List environments ~44
Environments (base URL, whether writes are allowed and why), auth profiles, databases and fixtures from .qa-mcp/api-test.yaml, plus the flows in tests/api/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_db Query test database ~71
Run one read-only query (SELECT/WITH/SHOW/EXPLAIN) against a configured test database, with :named params. Masked columns are shown as •••. Use it to find test data and write db checks.
| Name | Type | Req | Description |
|---|---|---|---|
| database | – | – | – |
| params | – | – | – |
| sql | string | yes | – |
No output schema declared.
No examples provided.
run_flows Run flows ~74
Run flows (default: everything in tests/api/) against an environment. Returns per-flow results with the failing checks and the request/response or query evidence; writes Markdown, JSON and JUnit reports.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | – | – | – |
| paths | – | – | – |
| tags | – | – | – |
| write_report | boolean | – | – |
No output schema declared.
No examples provided.
write_flow Write flow ~47
Save a YAML flow under tests/api/ after validating it. 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 Functional QA MCP server?
k11 API Functional QA runs locally as a PyPI package, launched with uvx k11-api-functional-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-functional-qa-mcp
claude mcp add k11-software-solutions-api-functional-qa -- uvx k11-api-functional-qa-mcp
What is the k11 API Functional QA MCP server?
k11 API Functional QA is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/api-functional-qa. Functional API tests: story-to-flow, negative tests from the spec, DB checks, evidence. This page covers its PyPI package (k11-api-functional-qa-mcp).
Is the k11 API Functional QA MCP server safe to use?
k11 API Functional QA scores 61 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 Functional QA MCP server expose?
k11 API Functional QA exposes 8 tools: list_environments, draft_flow, generate_negative_tests, write_flow, run_flows, and 3 more. Their descriptions and schemas cost roughly 612 tokens of context every time the server is loaded.
Is the k11 API Functional QA MCP server still maintained?
k11 API Functional 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 Functional QA MCP server under?
k11 API Functional 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 Functional QA MCP server?
VerifyMCP ran 14 checks on k11 API Functional QA, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about k11 API Functional QA: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.