Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

k11 Performance QA

PYPI · K11-PERFORMANCE-QA-MCP

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

78 Trust /100

Last scanned (15 hours ago)

Scores higher than 73% of PyPI servers

Category Testing and QA

Trust breakdown (7 categories)

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 32 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-performance-qa-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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 +15
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 19 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 +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.

  • 16 Nov 26 61

    First indexed and scored.

Diagnostics

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-performance-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-performance-qa-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/K11-Software-Solutions/k11techlab-performance-qa-mcp/.github/workflows/release.yml@refs/tags/v0.1.0
Rekor log index 3926995299
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:fa4063b2a0ab6b7617c16f80c3bdd747e248104d5aef8470c803bde972c037de

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 32 packages
Packages resolved 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~597 tokens

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 →

Tool Tokens
get_report ~53

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.

NameTypeReqDescription
endpoint–––

No output schema declared.

No examples provided.

import_jmeter_results ~161

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.

NameTypeReqDescription
compare_baselineboolean––
environment–––
pathstringyes–
save_as_baselineboolean––
scenario–––

No output schema declared.

No examples provided.

init_perf_config ~56

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

NameTypeReqDescription
overwriteboolean––

No output schema declared.

No examples provided.

perf_config ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_load_test ~176

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.

NameTypeReqDescription
compare_baselineboolean––
duration–––
engine–––
environment–––
max_rps–––
ramp_up–––
scenario–––
vus–––

No output schema declared.

No examples provided.

save_baseline ~97

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.

NameTypeReqDescription
duration–––
environment–––
from_last_runboolean––
scenario–––
vus–––

No output schema declared.

No examples provided.

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.

pypi · k11-performance-qa-mcp

# add to Claude Code
claude mcp add k11-software-solutions-performance-qa -- uvx k11-performance-qa-mcp
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.