k11 Release Gate
Ship, conditions, needs a person, or block: one release decision from QA evidence and policy.
- tools
- 5
- transport
- STDIO
- env var
- 1
- last updated
- Nov 13, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
evaluate_releaseThe verdict, every finding with its evidence, what wasn't tested; with `base_ref`, change-triggered evidence is required too. Writes `release-decision.md` / `.json`.
The verdict, every finding with its evidence, what wasn't tested; with `base_ref`, change-triggered evidence is required too. Writes `release-decision.md` / `.json`.
No parameter schema in public metadata yet.
plan_checksWhich evidence this change needs, from the files changed since a git ref and the policy's triggers.
Which evidence this change needs, from the files changed since a git ref and the policy's triggers.
No parameter schema in public metadata yet.
collect_evidenceWhat evidence exists: kind, file, age, SHA-256, key numbers, missing required kinds.
What evidence exists: kind, file, age, SHA-256, key numbers, missing required kinds.
No parameter schema in public metadata yet.
list_rulesEvery rule with its default and its outcome under your policy.
Every rule with its default and its outcome under your policy.
No parameter schema in public metadata yet.
init_policyWrites a commented starter policy (never overwrites without asking).
Writes a commented starter policy (never overwrites without asking).
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageConfiguration
QA_MCP_ROOTProject folder with the evidence and .qa-mcp/release-policy.yaml
Readme
k11 Release Gate — MCP server & CI gate
One release decision from all your QA evidence, under a policy you can read, with an audit trail.
Teams already have the evidence: UI test runs, API checks, security scans, JUnit files. What they lack is a consistent answer to "can we ship?". Today that answer is a person reading five dashboards under deadline pressure. k11 Release Gate reads the evidence, applies a written policy and returns one verdict, with every reason and the file it came from:
| Verdict | Meaning |
|---|---|
| 🟢 ship | nothing in the policy objects |
| 🟡 ship with conditions | ship, but someone must do something (e.g. approve the locator-heal PR) |
| 🟠 needs a person | ship only with sign-off from a named approver: risk-proportionate human-in-the-loop |
| 🔴 block | don't ship; here is each blocker and its evidence |
Details
- Repository
- github.com/k11-software-solutions/k11techlab-release-gate-mcp
- Website
- github.com/K11-Software-Solutions/k11techlab-release-gate-mcp
- Package
k11-release-gate-mcp- Transport
- STDIO
- Registry
- MCP registry, active