# k11 API Functional QA (pypi · k11-api-functional-qa-mcp)

Functional API tests: story-to-flow, negative tests from the spec, DB checks, evidence.

- Trust score: 61/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `k11-api-functional-qa-mcp`
- Version: `0.1.1`
- 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**: 50/100
  - Malware scan not yet available for this package.
  - 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 31 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-functional-qa-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 740 tokens (~92/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**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.

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "k11-software-solutions-api-functional-qa": {
      "command": "uvx",
      "args": [
        "k11-api-functional-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-13 (score 61)

First indexed and scored.

## MCP tools (8)

### `list_environments` (~44 tokens)

List environments

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/.

### `draft_flow` (~58 tokens)

Draft flow from a user story

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).

Input parameters:

- `spec`
- `story` (string, required)

### `generate_negative_tests` (~151 tokens)

Generate negative tests

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.

Input parameters:

- `base_values`
- `endpoint` (string, required)
- `fixtures`
- `spec`

### `write_flow` (~47 tokens)

Write flow

Save a YAML flow under tests/api/ after validating it. Won't overwrite unless asked.

Input parameters:

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

### `run_flows` (~74 tokens)

Run flows

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.

Input parameters:

- `environment`
- `paths`
- `tags`
- `write_report` (boolean)

### `call_api` (~101 tokens)

Call API

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.

Input parameters:

- `auth`
- `body`
- `call` (string, required)
- `environment`
- `headers`
- `path_params`
- `query`

### `query_db` (~71 tokens)

Query test database

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.

Input parameters:

- `database`
- `params`
- `sql` (string, required)

### `export_pytest` (~66 tokens)

Export flow to pytest

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).

Input parameters:

- `path` (string, required)
- `write` (boolean)

## Diagnostics

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

## Score history

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

## Common questions

### 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.

## Links

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