# k11 Performance QA (pypi · k11-performance-qa-mcp)

Load tests from your API flows: latency SLOs and significant regressions as release evidence.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Registry: `pypi`
- Package: `k11-performance-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 32 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-performance-qa-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 745 tokens (~124/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Performance QA MCP server?

k11 Performance QA runs locally as a PyPI package, launched with uvx k11-performance-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-performance-qa -- uvx k11-performance-qa-mcp
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add k11-software-solutions-performance-qa -- uvx k11-performance-qa-mcp
```

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "k11-software-solutions-performance-qa": {
      "command": "uvx",
      "args": [
        "k11-performance-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 78, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-20 (score 63, −14)

- [security regression] Malware scan: pass → unverified

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

- [security improvement] Malware scan: unverified → pass

### 2026-11-18 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

First indexed and scored.

## MCP tools (6)

### `perf_config` (~54 tokens)

Performance config

Environments (and whether load is allowed and why), scenarios with their flows, SLOs, regression settings,
guardrails, the engine that would run (k6 if installed, else builtin) and the saved baselines.

### `run_load_test` (~176 tokens)

Run load test

Run a load test and write .qa-mcp/perf-report/ (JSON evidence for the Release Gate, Markdown, samples).
Returns the verdict, findings (server errors, SLO breaches, statistically significant regressions), per-endpoint
latency (p50/p95/p99), errors and throughput, and the baseline comparison. Overrides (vus, duration like '30s',
ramp_up, max_rps, engine 'k6'|'builtin') are still capped by the guardrails. Refused on production-like
environments and when data-changing flows target a read-only environment.

Input parameters:

- `compare_baseline` (boolean)
- `duration`
- `engine`
- `environment`
- `max_rps`
- `ramp_up`
- `scenario`
- `vus`

### `save_baseline` (~97 tokens)

Save baseline

Save the baseline later runs are compared with. from_last_run=True uses the last completed run's samples
(.qa-mcp/perf-report/samples.json); otherwise runs the scenario now and saves it. Do this on main or a release
you trust, not on the branch under test.

Input parameters:

- `duration`
- `environment`
- `from_last_run` (boolean)
- `scenario`
- `vus`

### `import_jmeter_results` (~161 tokens)

Import JMeter results

Analyse an existing JMeter results file (.jtl, CSV with a header row or XML) inside the project exactly like a
run of our own: per-endpoint latency (endpoints are sampler labels; name them 'GET /orders/{id}'), SLOs, the
baseline comparison and findings, written to .qa-mcp/perf-report/ for the Release Gate. scenario defaults to
'jmeter'; use the same scenario and environment for the baseline and later imports. save_as_baseline=True
stores these results as the baseline instead of comparing.

Input parameters:

- `compare_baseline` (boolean)
- `environment`
- `path` (string, required)
- `save_as_baseline` (boolean)
- `scenario`

### `get_report` (~53 tokens)

Get report

The last run's report. With endpoint ('GET /orders/{id}'), that endpoint's full detail: latency
percentiles, status codes, SLO results, baseline comparison and example errors.

Input parameters:

- `endpoint`

### `init_perf_config` (~56 tokens)

Create performance config

Write a starter .qa-mcp/perf.yaml (scenario, profile, SLOs, regression settings, guardrails). Environments
and auth stay in .qa-mcp/api-test.yaml.

Input parameters:

- `overwrite` (boolean)

## Diagnostics

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

## Score history

- 2026-11-21: 78
- 2026-11-20: 63
- 2026-11-19: 77
- 2026-11-18: 62
- 2026-11-17: 61
- 2026-11-16: 61

## Common questions

### What is the k11 Performance QA MCP server?

k11 Performance QA is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/performance-qa. Load tests from your API flows: latency SLOs and significant regressions as release evidence. This page covers its PyPI package (k11-performance-qa-mcp).

### Is the k11 Performance QA MCP server safe to use?

k11 Performance QA scores 78 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 Performance QA MCP server expose?

k11 Performance QA exposes 6 tools: perf_config, run_load_test, save_baseline, import_jmeter_results, get_report, init_perf_config. Their descriptions and schemas cost roughly 597 tokens of context every time the server is loaded.

### Is the k11 Performance QA MCP server still maintained?

k11 Performance 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 Performance QA MCP server under?

k11 Performance 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 Performance QA MCP server?

VerifyMCP ran 16 checks on k11 Performance QA, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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-performance-qa-mcp/
- Socket report: https://socket.dev/pypi/package/k11-performance-qa-mcp
- Repository: https://github.com/K11-Software-Solutions/k11techlab-performance-qa-mcp
- Changelog RSS feed: https://verifymcp.io/servers/k11-software-solutions-performance-qa/k11-performance-qa-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/k11-software-solutions-performance-qa/k11-performance-qa-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/k11-software-solutions-performance-qa/k11-performance-qa-mcp.json
- HTML version of this page: https://verifymcp.io/servers/k11-software-solutions-performance-qa/k11-performance-qa-mcp
