k11 API Security QA
PYPI · K11-API-SECURITY-QA-MCP
OWASP API Top 10 tests from your OpenAPI spec, plus scanner SARIF judged for release.
Available components
Last scanned (19 hours ago)
Scores higher than 54% of PyPI servers
Category Security
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 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-api-security-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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 485 tokens (~80/item across 6 items; 6 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 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
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.
- 17 Nov 26 62
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-security-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-security-qa-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/K11-Software-Solutions/k11techlab-api-security-qa-mcp/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3941240876 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8b5d11481335819f50531a29a0acea9ceacabccd448e205d13c30edebde5ba4d |
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 →
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 →
get_report Get report ~35
The last security report, or one check's tests and findings with full evidence (requests, statuses, excerpts).
| Name | Type | Req | Description |
|---|---|---|---|
| check | – | – | – |
No output schema declared.
No examples provided.
init_security_config Create security config ~36
Write a starter .qa-mcp/security.yaml (identities, resources, admin paths, checks).
| Name | Type | Req | Description |
|---|---|---|---|
| overwrite | boolean | – | – |
No output schema declared.
No examples provided.
judge_scanner_results Judge scanner results ~75
Read SARIF from the paths in security.yaml (Semgrep, CodeQL, Trivy, Gitleaks, ZAP, Checkov...) and say which findings are new compared with the baseline, which are accepted (owner, reason, expiry) and which acceptances have expired. No requests are sent.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_security_tests Run security tests ~125
Run the OWASP API Top 10 checks on a test environment (refused on production-like names) and judge scanner SARIF results; writes .qa-mcp/security-report/ (JSON evidence for the Release Gate, Markdown for the PR). Returns the verdict, findings with evidence and fixes, and tests that failed or were inconclusive. checks: any of auth, bola, bfla, mass_assignment, data_exposure, headers, errors, rate_limit.
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | – | – |
| environment | – | – | – |
| include_scanners | boolean | – | – |
No output schema declared.
No examples provided.
save_scanner_baseline Save scanner baseline ~36
Record the current scanner findings as the baseline (do this on main), so later runs count only findings a change introduces.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
security_config Security config ~48
What will be tested: environment (and whether data-changing tests may run), identities and their auth profiles, test resources, admin-only operations, enabled checks, scanner result files, baseline and accepted risks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the k11 API Security QA MCP server?
k11 API Security QA runs locally as a PyPI package, launched with uvx k11-api-security-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-security-qa-mcp
claude mcp add k11-software-solutions-api-security-qa -- uvx k11-api-security-qa-mcp
What is the k11 API Security QA MCP server?
k11 API Security QA is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/api-security-qa. OWASP API Top 10 tests from your OpenAPI spec, plus scanner SARIF judged for release. This page covers its PyPI package (k11-api-security-qa-mcp).
Is the k11 API Security QA MCP server safe to use?
k11 API Security QA scores 62 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 Security QA MCP server expose?
k11 API Security QA exposes 6 tools: security_config, run_security_tests, judge_scanner_results, save_scanner_baseline, get_report, init_security_config. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Is the k11 API Security QA MCP server still maintained?
k11 API Security 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 Security QA MCP server under?
k11 API Security 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 Security QA MCP server?
VerifyMCP ran 14 checks on k11 API Security 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 Security 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.