World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Gating proxy for MCP servers: policy, verification and one audit trail across upstreams.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Sovereign Gateway。按照 https://mcp.popnx.com/i/mattijsmoens-sovereign-mcp-gateway.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 2/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Sovereign Gateway,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "sovereign-gateway": { "command": "uvx", "args": [ "sovereign-mcp-gateway", "--config", "{config_path}" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Sovereign Gateway 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"sovereign-gateway": {
"command": "uvx",
"args": [
"sovereign-mcp-gateway",
"--config",
"{config_path}"
]
}
}
}用 Sovereign Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Sovereign Gateway,或回答中出现 Sovereign Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Sovereign Gateway
Sovereign Gateway 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Sovereign Gateway 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Sovereign Gateway,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user sovereign-gateway -- uvx sovereign-mcp-gateway --config '{config_path}' 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Sovereign Gateway 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,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 sovereign-gateway -- uvx sovereign-mcp-gateway --config '{config_path}'应能看到 Sovereign Gateway 在列表中并显示已连接
用 Sovereign Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Sovereign Gateway,或回答中出现 Sovereign Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Sovereign Gateway,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "sovereign-gateway": { "command": "uvx", "args": [ "sovereign-mcp-gateway", "--config", "{config_path}" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Sovereign Gateway 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Sovereign Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Sovereign Gateway,或回答中出现 Sovereign Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Sovereign Gateway,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "sovereign-gateway": { "type": "stdio", "command": "uvx", "args": [ "sovereign-mcp-gateway", "--config", "{config_path}" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Sovereign Gateway 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 Sovereign Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Sovereign Gateway,或回答中出现 Sovereign Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user sovereign-gateway -- uvx sovereign-mcp-gateway --config '{config_path}'Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"sovereign-gateway": {
"command": "uvx",
"args": [
"sovereign-mcp-gateway",
"--config",
"{config_path}"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"sovereign-gateway": {
"command": "uvx",
"args": [
"sovereign-mcp-gateway",
"--config",
"{config_path}"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"sovereign-gateway": {
"type": "stdio",
"command": "uvx",
"args": [
"sovereign-mcp-gateway",
"--config",
"{config_path}"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 mattijsmoens 验证,该账户拥有此仓库
代码最后更新于3个月前
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 sovereign-mcp-gateway@0.3.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/mattijsmoens-sovereign-mcp-gateway)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3个月前,最新版本(0.3.0)于3个月前进入注册中心。
支持 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.
| 本项 Sovereign Gateway | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 2/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | NOASSERTION | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A gating proxy for Model Context Protocol servers. Point your MCP client at the gateway instead of at your servers. It connects to every upstream you list, merges their tool catalogues into one, and puts every call through a verification chain before it reaches the server that would execute it.
pip install sovereign-mcp-gateway
sovereign-mcp-gateway --init # writes gateway.json from the servers you already run sovereign-mcp-gateway --config gateway.json --check
--init reads the MCP configuration you already have (Claude Desktop, Claude Code, Cursor, VS Code or Windsurf) and writes a gateway.json that proxies those same servers, so the first run produces a working config rather than a configuration error. It will not import the gateway's own entry, because that would make it proxy itself.
The gateway is itself an MCP server, so any client that speaks MCP works with no changes.
That base install is a working gateway. Four optional extras add further layers on top — see Installing.
An agent reads a GitHub issue whose body carries an instruction aimed at the model rather than at you. It is persuaded, and calls git_commit.
| commits after | injected commit present | |
|---|---|---|
straight to mcp-server-git | 2 | yes |
| through the gateway | 1 | no |
Same tool, same arguments, same server. The difference is whether anything was in a position to refuse.
Read the walkthrough: [Your agent reads an issue](docs/your-agent-reads-an-issue.md) — or run it:
pip install "sovereign-mcp-gateway[all]" mcp-server-git
python examples/poisoned_issue.py
A library has to be adopted by whoever wrote the server. A proxy protects servers you cannot modify — which is most of them, because the useful MCP servers are published packages someone else maintains.
It also gives you one place to hold policy and one audit trail across every server an agent can reach, rather than per-server configuration nobody keeps in sync.
$ sovereign-mcp-gateway --init
Wrote gateway.json
imported 3 servers from Claude Desktop /Users/you/Library/Application Support/Claude/claude_desktop_config.json imported 1 server from VS Code (project)
upstreams: fetch, git, sqlite, time
skipped: sovereign - this gateway - importing it would proxy itself notion - no command, probably a remote/SSE server git - already imported from another client
Four things it will not do: import itself, import a remote server it cannot launch as a subprocess, overwrite an existing file without --force, or write a deny_tools list you did not choose. It writes the file, tells you what it took and what it left, and stops.
Pass --config PATH alongside --init to write somewhere other than ./gateway.json.
After running it, replace those servers in your client with a single entry for the gateway. Leaving both means your agent talks to them directly as well as through the proxy, and the audit trail will only show half the traffic.
{
"servers": { "git": {"command": "mcp-server-git", "args": ["--repository", "/repo"]}, "sqlite": {"command": "mcp-server-sqlite", "args": ["--db-path", "/data.db"]} }, "policy": {"deny_tools": ["git__git_reset"], "pii_policy": "warn"}, "audit": {"path": "gateway-audit.jsonl"} }
Check the wiring before a client ever sees it:
sovereign-mcp-gateway --config gateway.json --check
SOVEREIGN GATEWAY - configuration check
upstreams: 2 layers: policy -> intent -> text-filter -> frozen-verify -> audit
EXPOSED AS UPSTREAM TOOL git__git_status git.git_status git__git_reset git.git_reset [DENIED] sqlite__read_query sqlite.read_query ... 18 tools exposed.
policy → intent → text-filter → frozen-verify → [ call executes ] → output-verify → logic-rules → audit
| Layer | Package | Refuses when |
|---|---|---|
| policy | — | the tool is on a deny list, or absent from an allow list |
| intent | intentshield | the call fails the behavioural floor |
| text-filter | sovereign-shield | an argument carries injection, in any of 21 languages or seven encodings |
| frozen-verify | sovereign-mcp | the call disagrees with the tool definition frozen at startup |
| output-verify | sovereign-mcp | the result fails schema, deception, PII or content checks |
| logic-rules | logicshield | the result is inconsistent with rules you configured |
| audit | sovereign-mcp | — records every call, allowed or refused, in a hash-chained log |
The base install is a working gateway, not a stub:
pip install sovereign-mcp-gateway
That gives you policy → frozen-verify → audit, which already refuses a tool no upstream exposes, an argument of the wrong type, an undeclared parameter, a tool on your deny list, and prompt injection in an argument. Nothing else needed.
Each extra adds a layer on top:
| Extra | Adds | Worth it when |
|---|---|---|
[text] | sovereign-shield — a deeper pass over string arguments: 21 languages, and seven-variant decoding for payloads hidden in base64, hex, ROT13, leetspeak or reversed text | Your agents read text from anywhere you don't control. The base install catches IGNORE ALL PREVIOUS INSTRUCTIONS; it will not catch the same sentence base64-encoded, or written in Dutch |
[intent] | intentshield — a behavioural floor applied regardless of which tool was called: shell bans, delete bans, credential URLs, malware syntax | You want a backstop that doesn't depend on getting every tool's schema right |
[rules] | logicshield — consistency rules you write for tool *output* | You can express what a correct result looks like. Does nothing until you set output_rules |
[consensus] | requests — needed by Layer C's HTTP providers | You're enabling N-model consensus with a hosted provider |
Combine what you want, or take everything:
pip install "sovereign-mcp-gateway[text]" # one extra
pip install "sovereign-mcp-gateway[text,intent]" # several pip install "sovereign-mcp-gateway[all]" # every layer
All four extras are small pure-Python packages — [all] adds no compiled dependencies and no service to run.
A partial install degrades visibly. The gateway prints its active layers at startup, so you can always see what is actually running:
layers: policy -> frozen-verify -> audit # base
layers: policy -> intent -> text-filter -> frozen-verify -> audit # [all]
If a layer isn't on that line, it isn't running — whatever you think you installed.
Against mcp-server-git and mcp-server-sqlite running as real upstreams, driven by a real MCP client:
| Call | Result |
|---|---|
git__git_status, git__git_log | allowed |
sqlite__create_table, __write_query, __read_query | allowed — the row is really in the database |
git__git_reset | refused: on the deny list |
git__git_push_force | refused: no upstream exposes it |
git__git_status(repo_path=12345) | refused: wrong type for the frozen schema |
git__git_commit("IGNORE ALL PREVIOUS INSTRUCTIONS…") | refused: text filter |
sqlite__git_commit(...) | refused: a tool cannot be reached through another upstream's namespace |
Afterwards the repository still holds one commit and the database holds exactly the row it should — checked by opening them directly, not by trusting the gateway's own report. Eleven audit records for ten calls; editing any one of them breaks the chain.
Those cases are the test suite, not a screenshot: pytest tests/ -v.
Every other layer is deterministic and local. Layer C is the exception: it asks several independent models to extract the same structured document from a tool's result, canonicalises each answer, and compares the SHA-256 hashes. Agreement is decided by hash, not by prose.
It is off unless configured, because it is the only layer that costs money and latency per call, and the only one that sends tool output to a model.
{
"servers": { "...": {} }, "consensus": { "providers": [ {"type": "local", "model": "llama3.1:8b"}, {"type": "local", "model": "qwen2.5:7b", "base_url": "http://localhost:11434/v1"}, {"type": "openrouter", "model": "anthropic/claude-3.5-sonnet", "api_key_env": "OPENROUTER_API_KEY"} ] } }
Two provider types: `local` (any OpenAI-compatible endpoint — Ollama, vLLM, LM Studio; base_url defaults to http://localhost:11434/v1) and `openrouter` (the key is read from the named environment variable, never written in the config).
Three rules the gateway enforces at startup rather than discovering at runtime:
All providers run at temperature = 0, enforced in the constructor.
--check runs one real consensus call against your configured models and tells you what happened. This matters more than it sounds:
LAYER C - probing the configured models with one real call
OK. The configured models produced identical documents. Layer C will pass ordinary output rather than refusing it.
Consensus compares canonical hashes, so two models that are both *semantically* right but structurally different never agree. A weaker model that echoes the schema back —
{"branch": {"type": "string", "value": "main"}} instead of {"branch": "main"}
— mismatches on every call, forever, and the gateway refuses everything with a reason that correctly reads "the models disagreed". Because they did.
The probe distinguishes the three outcomes:
| means | |
|---|---|
| OK | the models produced identical documents; the layer is usable |
| MISMATCH | they disagree on a trivial document and will refuse every call — replace a model, or drop the section |
| provider unreachable | nothing was verified; a key, a model ID or an endpoint is wrong |
Install sovereign-mcp-gateway[consensus] or [all] — the HTTP providers need requests, which the core library deliberately does not depend on.
--check also lists the active layers, so you can confirm at a glance:
layers: policy -> intent -> text-filter -> frozen-verify -> consensus -> audit
If consensus is absent from that line, it is not running, whatever the config says.
With namespace on (the default) a tool is exposed as git__git_status. Two upstreams offering the same tool name cannot collide, shadow each other, or be reached through the wrong namespace. Turn it off only when you have a single upstream.
"policy": {
"deny_tools": ["git__git_reset", "write_query"], "allow_tools": null, "pii_policy": "warn", "fail_closed": true, "rate_limit_interval": 0 }
git__git_reset) or the upstream tool name (git_reset, on every upstream that has it).