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 Release Gate

PYPI · K11-RELEASE-GATE-MCP

Ship, conditions, needs a person, or block: one release decision from QA evidence and policy.

+19 this week 81 Trust /100

Last scanned (15 hours ago)

Scores higher than 80% 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 29 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-release-gate-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 Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 373 tokens (~74/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 +16
    • Malware scan: unverified → pass ▲ security
  • 20 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 19 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: fail → unverified ▼ functional
  • 17 Nov 26 +1
    • Package version: 0.3.0 → 0.4.0 functional
  • 16 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.3.0 functional
  • 13 Nov 26 62

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

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

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~280 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
collect_evidence ~42

Find the QA reports the policy points to: what each is, when it was produced, its SHA-256 and key numbers, and which required kinds are missing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

evaluate_release ~91

Decide whether to release: ship | ship_with_conditions | needs_human (named approvers) | block, with every rule that fired, the evidence it came from, and what wasn't tested. With base_ref, evidence kinds triggered by the changed files become required too. Writes release-decision.md/.json.

NameTypeReqDescription
base_ref–––
label–––
write_reportboolean––

No output schema declared.

No examples provided.

init_policy ~45

Write a commented starter policy to .qa-mcp/release-policy.yaml (defaults for every rule). Won't overwrite an existing policy unless asked.

NameTypeReqDescription
overwriteboolean––

No output schema declared.

No examples provided.

list_rules ~34

Every rule, its default outcome and the outcome under the project's policy (block | needs_human | conditional | info | off).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_checks ~68

Which kinds of evidence this change needs, from the files changed since base_ref and the policy's triggers (plus kinds the policy always requires), with the matching files and the K11 tool that produces each.

NameTypeReqDescription
base_refstring––
include_uncommittedboolean––

No output schema declared.

No examples provided.

Install

How do I install the k11 Release Gate MCP server?

k11 Release Gate runs locally as a PyPI package, launched with uvx k11-release-gate-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-release-gate-mcp

# add to Claude Code
claude mcp add k11-software-solutions-release-gate -- uvx k11-release-gate-mcp
Common questions

What is the k11 Release Gate MCP server?

k11 Release Gate is an MCP server listed in the public MCP registry as io.github.K11-Software-Solutions/release-gate. Ship, conditions, needs a person, or block: one release decision from QA evidence and policy. This page covers its PyPI package (k11-release-gate-mcp).

Is the k11 Release Gate MCP server safe to use?

k11 Release Gate scores 81 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 Release Gate MCP server expose?

k11 Release Gate exposes 5 tools: list_rules, collect_evidence, plan_checks, evaluate_release, init_policy. Their descriptions and schemas cost roughly 280 tokens of context every time the server is loaded.

Is the k11 Release Gate MCP server still maintained?

k11 Release Gate 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 Release Gate MCP server under?

k11 Release Gate 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 Release Gate MCP server?

VerifyMCP ran 16 checks on k11 Release Gate, 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.