World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Ship, conditions, needs a person, or block: one release decision from QA evidence and policy.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 k11 Release Gate。按照 https://mcp.popnx.com/i/k11-software-solutions-release-gate.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月17日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server k11 Release Gate,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "release-gate": { "command": "uvx", "args": [ "k11-release-gate-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Release Gate 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"release-gate": {
"command": "uvx",
"args": [
"k11-release-gate-mcp"
]
}
}
}用 k11 Release Gate 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 k11 Release Gate,或回答中出现 k11 Release Gate 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
QA_MCP_ROOT 包含证据文件和 .qa-mcp/release-policy.yaml 的项目文件夹 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 k11 Release Gate
k11 Release Gate 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 k11 Release Gate 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server k11 Release Gate,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user release-gate -- uvx k11-release-gate-mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Release Gate 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user release-gate -- uvx k11-release-gate-mcp应能看到 k11 Release Gate 在列表中并显示已连接
用 k11 Release Gate 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 k11 Release Gate,或回答中出现 k11 Release Gate 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
QA_MCP_ROOT 包含证据文件和 .qa-mcp/release-policy.yaml 的项目文件夹 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server k11 Release Gate,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "release-gate": { "command": "uvx", "args": [ "k11-release-gate-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Release Gate 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 k11 Release Gate 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 k11 Release Gate,或回答中出现 k11 Release Gate 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
QA_MCP_ROOT 包含证据文件和 .qa-mcp/release-policy.yaml 的项目文件夹 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server k11 Release Gate,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "release-gate": { "type": "stdio", "command": "uvx", "args": [ "k11-release-gate-mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 k11 Release Gate 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 k11 Release Gate 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 k11 Release Gate,或回答中出现 k11 Release Gate 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
QA_MCP_ROOT 包含证据文件和 .qa-mcp/release-policy.yaml 的项目文件夹 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user release-gate -- uvx k11-release-gate-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"release-gate": {
"command": "uvx",
"args": [
"k11-release-gate-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"release-gate": {
"command": "uvx",
"args": [
"k11-release-gate-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"release-gate": {
"type": "stdio",
"command": "uvx",
"args": [
"k11-release-gate-mcp"
]
}
}
}QA_MCP_ROOT env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 K11-Software-Solutions 验证,该账户拥有此仓库
代码最后更新于前天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/k11-software-solutions-release-gate)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(0.4.0)于前天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 k11 Release Gate | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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 |
Deterministic. The same evidence and the same policy always give the same verdict. There's no LLM in the decision, so it holds up in an audit. Every evidence file is recorded with its SHA-256, timestamp and age, alongside the policy's own hash and the git commit.
The kind of evidence is recognised from the file's content:
| Evidence | Produced by |
|---|---|
UI tests with self-healing (heal-report.json) | k11 Playwright QA or k11 Selenium QA heal-ci |
API contract (contract-report.json) | k11 API Contract QA contract-ci |
API functional tests (api-test-report.json) | k11 API Functional QA run |
LLM red-team (assessment.json) | LLM Assure |
Performance under load (perf-report.json) | k11 Performance QA run |
Security: OWASP API tests and scanner SARIF (security-report.json) | k11 API Security QA run |
Integration: API, Kafka, batch job and database flows (integration-report.json) | k11 Integration QA run |
| Any JUnit XML | pytest, Maven Surefire, Gradle, Jest, Playwright, … |
k11-release-gate-mcp plan --base origin/main
The gate compares the branch with --base and maps the changed files to evidence kinds using the policy's triggers (sensible defaults included): an openapi.yaml change needs contract and API evidence, .tsx/.css/templates need UI evidence, prompts/** needs an LLM red-team. evaluate --base origin/main then requires exactly those kinds, so a CSS-only change isn't held up by a red-team, and an API change can't ship without a contract check. The plan is saved in the decision record, so "why was this check required?" always has an answer.
triggers: # override the defaults per kind
llm: ["src/assistant/", "prompts/"] contract: ["api/openapi.yaml"]
Missing evidence is never treated as a pass. Required kinds that are missing block by default, and optional kinds without evidence are listed as not tested.
demo/ contains two release candidates whose evidence comes from real runs of the five K11 tools against their own demos.
rc1 → 🔴 Block, with 7 blockers, each traced to its source:
- 1 UI test failed for reasons other than locators (
ui.real_failures): page title changed
- 2 broken locators still unresolved (
ui.unresolved_locators): "Edit profile" needs review;cart-btnheal reverted
- API change breaks billing-svc, checkout-web, notification-svc (
contract.breaks_critical_consumer): billing-svc is critical, owner @team-billing
- 2 API flows failed (
api.flow_failed): "Order total is quantity times price", negative tests forPOST /orders
- 2 server errors (5xx) in API tests (
api.server_error): wrong type / missingitems[0].qty
- 6 critical and 13 high-severity LLM findings (
llm.critical,llm.high): unverified refund, other customers' records, indirect prompt injection, …
Needs a person: the contract check escalated (3 consumers break). Conditions: approve the healed
view-orderslocator; confirm the consumer list for 3 unused breaking changes.
rc2 (after the fixes) → 🟠 Needs a person's sign-off:
Sign-off needed from @qa-lead, @ai-safety-lead before release.
- Needs a person: 1 LLM probe inconclusive (
llm.inconclusive)
- Condition: 1 locator healed and verified: approve the heal pull request
Everything passes, but one security probe couldn't be decided automatically, so the policy asks a named person to look. It doesn't let it through silently and doesn't block the release outright.
QA_MCP_ROOT=demo/rc1 k11-release-gate-mcp evaluate --label rc1
QA_MCP_ROOT=demo/rc2 k11-release-gate-mcp evaluate --label rc2
.qa-mcp/release-policy.yamlname: Order platform release policy
evidence: # where each tool writes its report (globs inside the project) api_tests: [".qa-mcp/api-test-report/api-test-report.json"] junit: ["test-results/**/*.xml"] required: [api_tests, contract, ui_heal, llm] max_age_hours: 24 # older evidence → evidence.stale critical_consumers: [critical, high] # their breakage blocks approvers: ["@qa-lead", "@ai-safety-lead"] # named on a needs_human verdict rules: # override any rule: block | needs_human | conditional | info | off llm.medium: needs_human ui.healed: info
k11-release-gate-mcp init writes a commented starter policy; k11-release-gate-mcp rules lists every rule.
| Rule | Default | Fires when |
|---|---|---|
evidence.missing | block | a required kind has no evidence |
evidence.unreadable | needs a person | an evidence file can't be parsed |
evidence.stale | condition | evidence is older than max_age_hours |
api.server_error | block | an API returned a 5xx during functional tests |
api.flow_failed | block | an API flow failed |
api.flow_not_run | needs a person | a flow was blocked by guardrails or errored, so it proved nothing |
contract.breaks_critical_consumer | block | an API change breaks a consumer in critical_consumers |
contract.breaks_consumer | needs a person | it breaks another consumer |
contract.escalation | needs a person | the contract check asked for a person |
contract.breaking_unused | condition | breaking changes with no known consumer |
ui.real_failures | block | UI tests failed for reasons other than locators |
ui.unresolved_locators | block | broken locators were reverted, need review or weren't found |
ui.healed | condition | locators were healed and verified; approve the heal PR |
ui.suggested | condition | heals were suggested in a dry run |
llm.critical, llm.high | block | LLM security findings at that severity |
llm.medium | condition | medium findings |
llm.inconclusive | needs a person | probes that need review or errored |
llm.low | note | low findings |
perf.server_errors | block | 5xx responses under load |
perf.slo_breached | block | an endpoint missed a latency, error-rate or throughput SLO |
perf.aborted | block | the load test stopped because too many requests failed |
perf.regression | needs a person | significantly slower (or more errors) than the baseline |
perf.not_run | needs a person | the load test was refused by guardrails or didn't start |
perf.no_baseline, perf.insufficient_samples | note | regressions couldn't be checked |
security.critical, security.high | block | API security findings, or new scanner findings, at that severity |
security.acceptance_expired | needs a person | an accepted risk passed its expiry date |
security.not_run | needs a person | the security run was refused or failed |
security.medium | condition | medium findings: plan a fix |
security.inconclusive | note | security tests that couldn't prove a result |
integration.failed | block | an integration flow failed: event missing or wrong, consumer effect, dead-letter queue, job |
integration.flows_not_run | needs a person | flows refused (writes not allowed, protected topic) or errored |
integration.not_run | needs a person | no integration flows ran |
junit.failures | block | failures or errors in any JUnit file |
junit.skipped | note | skipped tests |
| Tool | What it does |
|---|---|
evaluate_release | 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. |
plan_checks | Which evidence this change needs, from the files changed since a git ref and the policy's triggers. |
collect_evidence | What evidence exists: kind, file, age, SHA-256, key numbers, missing required kinds. |
list_rules | Every rule with its default and its outcome under your policy. |
init_policy | Writes a commented starter policy (never overwrites without asking). |
The Claude Code plugin adds /release-check, which collects the evidence, tells you which tool produces anything missing, evaluates and explains, without ever softening the verdict.
k11-release-gate-mcp evaluate --label v2.4.0 --base origin/main
It writes release-decision.md (the PR comment) and release-decision.json (the audit record), sets GitHub Actions outputs (verdict, blockers, needs_human, conditions, report) and exits non-zero according to --fail-on block | needs-human | conditions | never. See docs/release-gate.yml.
/plugin marketplace add K11-Software-Solutions/k11techlab-release-gate-mcp
/plugin install release-gate@k11-release-gate
Or the MCP server only: claude mcp add release-gate -- uvx k11-release-gate-mcp, or pip install k11-release-gate-mcp for CI.
This puts into practice the risk-proportionate human-in-the-loop idea from the K11 research on autonomous CI/CD quality assurance (IJECS, 2026): automate the clear cases and send the uncertain ones to a named person, with the evidence attached. It's an independent implementation and doesn't depend on the research code.
python -m venv .venv && .venv/Scripts/pip install -e ".[dev]" # bin/pip on macOS/Linux
pytest # real evidence from all eight tools, policy, determinism, diff-aware planning, CLI, MCP (27)
needs_human verdict, and when)plan_checks asks for through the K11 servers and asks this gate for the verdictBuilt by K11 Software Solutions. Part of the K11 Tech Lab agentic QA series. MIT licensed.