World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Streamable HTTP MCP gateway for NV oOS fleets — one API key, namespaced tools, quotas and policy.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 NV oOS Gateway。按照 https://mcp.popnx.com/i/nvdigitalsolutions-nvoos-mcp-gateway.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.nvoos.pro) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 5 分钟
需要 NV oOS Gateway 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
NV oOS Gatewayhttps://mcp.nvoos.pro/mcp在 Request headers 下添加这个名称和值
AuthorizationBearer <在这里粘贴你的密钥>只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsNV oOS Gateway
用 NV oOS Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 NV oOS Gateway,或回答中出现 NV oOS Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 NV oOS Gateway
NV oOS Gateway 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式
A · 使用能连接 NV oOS Gateway 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code · 约 5 分钟
需要 NV oOS Gateway 的密钥(在开发者网站创建)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user nvoos-gateway https://mcp.nvoos.pro/mcp --header 'Authorization: Bearer your-value'按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 NV oOS Gateway 在列表中并显示已连接
用 NV oOS Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 NV oOS Gateway,或回答中出现 NV oOS Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 5 分钟
需要 NV oOS Gateway 的密钥(在开发者网站创建)
在 NV oOS Gateway 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 NV oOS Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 NV oOS Gateway,或回答中出现 NV oOS Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 5 分钟
需要 NV oOS Gateway 的密钥(在开发者网站创建)
在 NV oOS Gateway 的设置中,Authorization 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 NV oOS Gateway 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 NV oOS Gateway,或回答中出现 NV oOS Gateway 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.nvoos.pro/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user nvoos-gateway https://mcp.nvoos.pro/mcp --header 'Authorization: Bearer your-value'Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"nvoos-gateway": {
"url": "https://mcp.nvoos.pro/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"nvoos-gateway": {
"type": "http",
"url": "https://mcp.nvoos.pro/mcp",
"headers": {
"Authorization": "Bearer your-value"
}
}
}
}Authorization 机密 必填 HTTP header说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 nvdigitalsolutions 验证,该账户拥有此仓库
代码最后更新于昨天
GitHub 无法识别许可证类型;请打开文件自行查看
在 161 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/nvdigitalsolutions-nvoos-mcp-gateway)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于昨天,最新版本(0.3.1)于14天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有: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.
| 本项 NV oOS Gateway | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/5 | 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 public, fleet-scoped Model Context Protocol endpoint for the NV oOS (Open Operator System) WordPress platform. One API key, every bound site — tools appear namespaced as _ .
The gateway is an MCP aggregating proxy speaking streamable HTTP (MCP 2026-07-28): it authenticates callers with a public API key, forwards initialize / tools/list / tools/call to the bound NV oOS sites' native /wp-json/mcp-ai/v1/mcp endpoints using Fleet Operator tokens, and keeps the fleet surface collision-free by prefixing tool names per site.
Deployment target: Cloudways Velocity (managed Node hosting) at https://mcp.nvoos.pro. See docs/operations/deployment/mcp-gateway-velocity-setup.md.
One-way mirror: this addon is the canonical source and is synced to
the standalone repo
nvdigitalsolutions/nvoos-mcp-gateway(branchmain)
by
sync-mcp-gateway.yml, which snapshots the subtree as one commit per
sync and pushes without `--force` — the mirror main stays a linear
fast-forward line, so hosting platforms (Cloudways Velocity) auto-deploy
on every sync. Never commit to the standalone repo directly — the next
sync overwrites it.
| Route | Auth | Purpose |
|---|---|---|
GET /mcp | public | Streamable-HTTP discovery JSON |
POST /mcp | Bearer key | JSON-RPC 2.0 (initialize, ping, notifications, tools/list, tools/call, resources/*, prompts/*) |
GET /health | public | Minimal status + per-site health registry |
GET /health/full | Bearer key | Full view (host-only URLs, bindings) |
GET /admin/policy | Operator token | Effective policy + quota table (read-only) |
POST /admin/policy-sim | Operator token | Replay a candidate policy against recorded calls |
GET /admin/catalog | Operator token | Fleet catalog with per-site lifecycle states |
GET / | public | Human landing page (directory reviewers) |
| Variable | Required | Purpose |
|---|---|---|
GATEWAY_PUBLIC_KEYS | yes | Public keys → site slugs: key=slug-a,slug-b;key2=slug-c (or JSON object) |
GATEWAY_PUBLIC_KEYS_PREVIOUS | no | Rotation overlap — previous key map (warns once on use) |
PUBLIC_SITE_SLUGS | no | Privacy filter for the public /health endpoint: comma-separated slugs visible without auth (* or unset = all configured sites). /health/full always reports every site. |
PUBLIC_DEMO_KEY | no | Operator-published demo key rendered on the GET / landing page (substituted into the copy-paste configs). A public, site-scoped credential — never a secret. Unset = the page keeps YOUR_KEY placeholders. |
NVOOS_SITE_ _URL | per site | Upstream MCP endpoint, full URL incl. /wp-json/mcp-ai/v1/mcp |
NVOOS_SITE_ _TOKEN | per site | Fleet Operator token (op_xxxx.SECRET); never logged or returned |
AUTH_MODE | no | strict (default) fails closed at boot when no keys are set |
UPSTREAM_TIMEOUT_MS | no | Per-site timeout for tools/list + notifications (default 20000) |
UPSTREAM_TOOL_TIMEOUT_MS | no | tools/call budget only — long-running tools get more room without slowing tools/list (default: UPSTREAM_TIMEOUT_MS) |
GATEWAY_OAUTH_ISSUER | no | OAuth 2.1 authorization server issuer (e.g. Auth0 tenant). Setting it turns the gateway into an RFC 9728 protected resource — see the OAuth section below |
GATEWAY_OAUTH_JWKS_URI | no | JWKS override (default: issuer's /.well-known/jwks.json) |
GATEWAY_OAUTH_RESOURCE | no | RFC 8707 resource identifier / token audience (default https://mcp.nvoos.pro) |
GATEWAY_OAUTH_DEFAULT_SITES | no | Fallback slugs for a valid OAuth token that carries no site: scope (ChatGPT's connector requests only AS-level OIDC scopes). Unset = such tokens get 403 insufficient_scope |
TRUST_PROXY | yes on Velocity | 1 — NGINX sets X-Forwarded-For |
ALLOWED_ORIGINS | no | Comma-separated CORS origins for browser-based clients |
MAX_JSON_BODY | no | Body limit (default 1mb) |
RATE_LIMIT_GLOBAL / _MCP / _HEALTH | no | Per-group budgets (defaults 600/5min, 120/min, 60/min) |
TOOL_QUOTAS | no | Per-tool quotas, compact form: : / : — e.g. delete_post:5/1h:2,woo_*:60/1m:*. Most-specific pattern wins. (Proposal 094) |
GATEWAY_POLICY | no | Policy ruleset (JSON string) — see the policy reference below. (Proposal 094) |
POLICY_FILE | no | Alternative: path to a JSON policy file (Git-versioned policy, read at boot). |
SHADOW_POLICY | no | Shadow ruleset (JSON string) — evaluated and logged, never enforced. |
GEO_MAP | no | JSON object mapping public key ids to ISO country codes (used when not behind a trusted proxy). |
GATEWAY_ADMIN_TOKEN | no | Operator token enabling the /admin/* surface (inert without it). |
AUDIT_SINK_URL / AUDIT_SINK_SECRET | no | HMAC-signed webhook for governance events (deny, quota_exceeded, call_ok…). Must be set together. |
SITE_LIFECYCLE | no | Per-site catalog states: slug-a:draft,slug-b:published (default published). |
Slug → env suffix mapping: site-a → NVOOS_SITE_SITE_A_* (uppercase, hyphens → underscores).
GATEWAY_PUBLIC_KEYS=demo-public-key-1234567890=demo-site
NVOOS_SITE_DEMO_SITE_URL=https://demo.example.com/wp-json/mcp-ai/v1/mcp NVOOS_SITE_DEMO_SITE_TOKEN=op_xxxx.SECRET AUTH_MODE=strict TRUST_PROXY=1
Per-tool quotas and declarative policy ride on top of the group budgets. Sites remain the deep enforcement layer (per-tool RPM, token budgets, iteration caps, capability boundaries, nefarious-usage auto-shutdown) — the gateway adds the fleet layer and can only tighten, never weaken.
TOOL_QUOTAS=delete_post:5/1h:2,woo_*:60/1m:*,*:600/5m:*
Breaches return HTTP 429 + RFC 9558 headers (RateLimit-Limit/Remaining/Reset, RateLimit-Policy) with the JSON-RPC error -32099. Buckets are scoped (key × site × tool) — one noisy key cannot exhaust another's budget.
{
"rules": [ { "id": "no-night-deletes", "effect": "deny", "tool": { "match": "delete_*" }, "time": { "window": { "tz": "Europe/London", "days": [1,2,3,4,5], "start": "09:00", "end": "17:00" } } } ] }
First match wins. Effects: deny (403 + -32001), require_approval (428 + -32002 with a redacted preview). Conditions: tool.match (glob), site, key, time.window (IANA tz, ISO weekdays 1–7, midnight-crossing windows), geo.country (ISO alpha-2). Denied tools are filtered out of tools/list entirely (kept out of model context).
dryRun: true on tools/call evaluates policy + quotas withoutexecuting or consuming — the result carries would_execute, policy, and quota.
POST /admin/policy-sim replays a candidate policy against the last 200recorded calls (argument keys only) and diffs it against the live policy.
SHADOW_POLICY evaluates in parallel and logs — never enforces.tools/list merges every site bound to the key and prefixes names with an underscore separator: site-a_create_post, site-b_woo_get_products. (The underscore is deliberate — the MCP tool-name grammar forbids dots, and OpenAI connectors normalize illegal names, breaking dot-prefixed round-trips.)tools/call accepts the prefixed name (always), a legacy dot-prefixed name from pre-0.2.1 listings, or a bare name when the key is bound to exactly one site (passthrough mode)._meta.gateway.errors entry instead of failing the whole call.resources/* and prompts/* use the first bound site.initialize echoes the highest protocol version both sides support (2026-07-28 → 2024-11-05), defaulting to 2024-11-05 when the client sends no version — strict clients (Zed, Claude Desktop) abort with "Unsupported protocol version" when the server hardcodes a version they do not speak.WWW-Authenticate.The addon ships a Claude Code plugin (.claude-plugin/plugin.json, commands/connect.md, skills/gateway/) that syncs to the mirror repo. The mirror doubles as the plugin's marketplace (.claude-plugin/marketplace.json), so it installs by name:
/plugin marketplace add nvdigitalsolutions/nvoos-mcp-gateway
/plugin install nvoos-mcp-gateway@nvoos-marketplace
Enabling the plugin prompts for the gateway API key (stored securely as a sensitive userConfig option) and substitutes it into the MCP server's Authorization header.
Release discipline: version in .claude-plugin/plugin.json must be bumped with every gateway release or installed plugins never see updates.
A slimmer, directory-ready distribution (nvoos-gateway, plugin-only files plus icon) ships in addons/claude-gateway-plugin/ and syncs to nvdigitalsolutions/nvoos-claude-gateway-plugin — use that for the Anthropic directory submission.
With GATEWAY_OAUTH_ISSUER set, the gateway acts as an RFC 9728 protected resource alongside static keys:
GET /.well-known/oauth-protected-resource (+ the /mcp path-insertion variant) serves the protected-resource metadata document (inert 404 when OAuth is unconfigured).WWW-Authenticate: Bearer resource_metadata="…", scope="…" so MCP clients can run the OAuth 2.1 authorization-code + PKCE flow against the configured authorization server.iss, aud (RFC 8707 resource binding), exp/nbf, and scope.site: scope grants access to that bound site (the read-only site:read scope is advertised for future fine-grained enforcement). Tokens granting no configured site get 403 insufficient_scope.Authorization server: any OAuth 2.1 AS with RFC 8414 metadata + JWKS (Auth0 is the platform convention). Dynamic client registration (RFC 7591) belongs to the AS, not the gateway.
ChatGPT connector notes (verified against the live production setup, 2026-11-01):
https://mcp.nvoos.pro/mcp — ChatGPT binds resource to the path-insertion metadata URL (RFC 9728 §3.3), and Auth0 matches it exactly.scopes_supported and expects an exact match in the token response (else OAUTH_SCOPES_MISMATCH) — a post-login Action (api.accessToken.addScope) grants the OIDC set.site:*, so pair the deployment with GATEWAY_OAUTH_DEFAULT_SITES= (e.g. demo) or the token is rejected 403 insufficient_scope. Explici