World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Claim-level provenance preflight for sanitized nonfiction passages; automated triage only.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 24/100 |
质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Mps Preflight。按照 https://mcp.popnx.com/i/maha-strategies-mps-preflight.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/5 项检查 · 你的提问会经过开发者的服务器(www.mahastrategies.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Mps Preflighthttps://www.mahastrategies.com/api/mcp/mps-preflight在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsMps Preflight
用 Mps Preflight 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Mps Preflight,或回答中出现 Mps Preflight 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Mps Preflighthttps://www.mahastrategies.com/api/mcp/mps-preflight开启新聊天,输入前先从插件列表中选择 Mps Preflight
用 Mps Preflight 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Mps Preflight,或回答中出现 Mps Preflight 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user mps-preflight https://www.mahastrategies.com/api/mcp/mps-preflight应能看到 Mps Preflight 在列表中并显示已连接
用 Mps Preflight 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Mps Preflight,或回答中出现 Mps Preflight 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Mps Preflight 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Mps Preflight,或回答中出现 Mps Preflight 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Mps Preflight 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Mps Preflight,或回答中出现 Mps Preflight 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://www.mahastrategies.com/api/mcp/mps-preflightJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user mps-preflight https://www.mahastrategies.com/api/mcp/mps-preflightCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mps-preflight": {
"url": "https://www.mahastrategies.com/api/mcp/mps-preflight"
}
}
}VS Code (mcp.json)
{
"servers": {
"mps-preflight": {
"type": "http",
"url": "https://www.mahastrategies.com/api/mcp/mps-preflight"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月16日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
mps_claim_preflightClassify substantive claims in a sanitized nonfiction passage using Maha Provenance Standard v0.1. Returns claim excerpts, provenance tags, and suggested actions. Do not submit sensitive, personal, regulated, or confidential material. This is automated triage, not factual verific
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 Maha-Strategies 验证,该账户拥有此仓库
代码最后更新于4天前
仓库中没有找到许可证文件
在 106 毫秒内响应(HTTP 200)
无需登录
已读取 1 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/maha-strategies-mps-preflight)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于4天前,最新版本(0.1.0)于4个月前进入注册中心。
支持 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.
| 本项 Mps Preflight | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | – | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
The Maha Strategies platform: one Next.js application serving the public site and publishing surfaces, the credentialed commercial APIs, and the private operations control planes behind them. It is deployed on Vercel at www.mahastrategies.com.
Most of what follows in this file is operating instructions for a specific subsystem — read the section you need rather than the whole document.
| Concern | Service |
|---|---|
| Application and hosting | Next.js (App Router), React, TypeScript, on Vercel |
| Database | Supabase Postgres, RLS with no public access policies |
| Cache, rate limits, balances | Upstash Redis, namespaced per deployment environment |
| GPU compute | Modal — workers/maha_workers.py |
| Payments | Stripe — a separate endpoint and signing secret per product line |
| Resend | |
| Telemetry | Sentry, payload-scrubbed |
Requires Node 22 or newer.
npm install
npm run dev
The app serves on http://localhost:3000. Copy .env.example to .env.local and fill in what the surface you are working on needs; most features degrade to a disabled state rather than crashing when their variables are absent.
To exercise the database locally, start Supabase (supabase start) and apply supabase/migrations plus supabase/seed.sql, which provides deterministic fixtures.
npm run typecheck && npm run lint && npm test
npm test runs the full suite in test/. The same commands run in CI on every pull request, together with a production build, a production-dependency audit, and the migration integrity check below.
Three rules are enforced rather than assumed, because violating them corrupts state that cannot be reconstructed:
<14-digit UTC timestamp>_ .sql and must sort after everything already on main. Verify with: node --experimental-strip-types scripts/check-migrations.ts
NEXT_PUBLIC_* variables reach the browser. Credential secrets are disclosed exactly once at issuance and stored only as hashes.Framework note: this repository tracks a Next.js version whose APIs may differ from older documentation. See AGENTS.md.
| Runbook | Covers |
|---|---|
docs/agent-discovery-metering.md | Measuring whether agents are finding the platform, and reading the numbers honestly |
docs/backup-restore.md | Rehearsing a database restore, and measuring RTO and RPO |
docs/database-migrations.md | Applying schema changes to Production, drift detection, evidence |
docs/observability.md | Sentry configuration, signed alert verification, readiness checks |
docs/release-recovery.md | Release health, recovery drill, rollback, rehearsal, required GitHub environments |
docs/preview-e2e.md | Integration gates on every Preview deployment, and making them block merges |
docs/slo-capacity.md | Service objectives, error budgets, the bounded capacity harness |
docs/x402-conformance-corpus.md | Vendor-neutral x402 v2 fixtures and the offline reference runner |
docs/x402-declaration-digest-proposal.md | Draft catalog-attested discovery declaration digest and test vectors |
docs/x402-doctor.md | Live resource, crawler, Bazaar drift, and bounded-settlement diagnostics |
docs/x402-observatory.md | Public protocol-correctness observations, inclusion policy, and scheduled operation |
docs/x402-buyer-policy.md | Vendor-neutral pre-signing budgets, approvals, replay controls, and settlement verification |
SECURITY.md | Vulnerability reporting and the platform's standing security assumptions |
The private Market Scout is a read-only discovery process. It pulls attributable web-search evidence into /admin/market-mapping, where every proposal remains subject to a deterministic score and human review. It cannot publish, spend, deploy, or contact a person.
With MARKET_SCOUT_SOURCES=exa and EXA_API_KEY set, the default matrix rotates five queries per UTC day across MPS claim verification, research briefs, document-data extraction, and receipt operations. Each query retrieves at most eight Exa results.
To replace the defaults, set this server-only JSON environment variable:
MARKET_SCOUT_QUERY_MATRIX={"lanes":[{"id":"claims","label":"Claim verification","queries":["claim verification API pricing","citation audit tool quote"]},{"id":"documents","label":"Document extraction","queries":["PDF table extraction API pricing"]}]}
The matrix permits up to eight named lanes and twelve queries per lane; the Scout still selects only five cross-lane queries per daily run. The older MARKET_SCOUT_QUERIES JSON-string-array setting remains supported as a single custom lane for backward compatibility.
POST /api/agent-inquiries is an authenticated, non-binding intake endpoint for the offers published in /agent-offers.json. It validates against /agent-inquiry-schema.json, persists the inquiry and its first event to a private Supabase ledger, then attempts to notify the reviewer through Resend. It does not accept payment, create a commission, or send work automatically.
The inquiry gateway accepts named, database-backed client credentials. Credential issuance and revocation are private reviewer operations; there is no shared public inquiry token.
Set these deployment environment variables before enabling it:
AGENT_REVIEW_TOKEN=<unique reviewer bearer token>
RESEND_API_KEY=
Optional delivery overrides are AGENT_INQUIRY_FROM and AGENT_INQUIRY_TO. Keep the reviewer token server-side. Client credentials are created by the private registry and are shown only once at issuance.
Approved clients send JSON using the schema at /agent-inquiry-schema.json:
curl --request POST https://www.mahastrategies.com/api/agent-inquiries \
--header "Authorization: Bearer $CLIENT_CREDENTIAL" \ --header "Content-Type: application/json" \ --data '{ "clientRequestId": "client-generated-unique-id", "offerId": "rapid-intelligence-brief", "requester": { "name": "Requesting principal", "email": "principal@example.com" }, "decision": "The decision this brief will inform.", "question": "One clearly defined market, technology, or policy question.", "requesterAuthorized": true, "agent": { "name": "Approved client agent", "version": "1.0" } }'
A successful 202 response means only that the request was recorded for human review. The returned notificationStatus shows whether the optional email notification was delivered. Neither result is an acceptance, purchase confirmation, or service-level commitment.
Apply supabase/migrations/20260716_agent_inquiry_ledger.sql, supabase/migrations/20260716_agent_client_credentials.sql, supabase/migrations/20260716_mps_audit_jobs.sql, and supabase/migrations/20260717_serverless_credential_rate_limits.sql in the Supabase SQL Editor before enabling the full agent infrastructure. Together, they create the private inquiry ledger, credential registry, MPS audit ledger, database-maintained event histories, and an atomic shared credential rate limiter with RLS and no public access policies. The existing NEXT_PUBLIC_SUPABASE_URL and SUPABASE_SERVICE_ROLE_KEY deployment variables are required.
Selected credential-based commercial APIs also write to commercial_api_usage_daily through 20260727000100_privacy_preserving_commercial_api_metering.sql. This is a daily aggregate meter for MPS audits, MPS credit reads, book-entitlement checks, and structured book-content delivery. It deliberately excludes IP addresses, user agents, token values or fingerprints, request and response bodies, referrers, emails, and visitor identifiers. The read-only aggregate board is /admin/commercial-api-metering and requires REVENUE_CONTROL_TOKEN.
Reviewer operations use a separate private endpoint:
GET /api/agent-inquiries/:inquiryId
PATCH /api/agent-inquiries/:inquiryId
Both require Authorization: Bearer . GET returns the full private request and its event history. PATCH accepts one action: start_review, needs_clarification, decline, or approve_for_scoping; the last is an internal disposition, not an acceptance of work.
Private reviewer operations are available at:
GET /api/agent-credentials
POST /api/agent-credentials GET /api/agent-credentials/:credentialId PATCH /api/agent-credentials/:credentialId
All require Authorization: Bearer . POST issues a credential once; its plaintext value is returned only in that response. Supply either a new clientName or an existing clientId, plus credentialLabel, one or more allowedOfferIds and/or optional allowedCapabilities, optional rateLimitPerHour (default 12), and optional expiresAt (default 90 days). A capability-only credential is permitted. Capabilities default to none; the only current capability is mps_audit. PATCH accepts { "action": "revoke", "reason": "optional note" }. GET endpoints never return a credential secret.
Example issuance:
curl --request POST https://www.mahastrategies.com/api/agent-credentials \
--header "Authorization: Bearer $AGENT_REVIEW_TOKEN" \ --header "Content-Type: application/json" \ --data '{ "clientName": "Example client agent", "credentialLabel": "Production research intake", "allowedOfferIds": ["rapid-intelligence-brief"], "allowedCapabilities": ["mps_audit"], "rateLimitPerHour": 12 }'
POST /api/mps-audits applies the headless MPS/0.1 engine to a single passage. It requires a named client credential carrying the explicit mps_audit capability, uses the same credential rate limit, and stores an idempotent audit record in Supabase. The source passage is processed but deliberately not retained; the record retains the input hash, output claim excerpts, model identifier, status, and event history. This is a computational API, not a certification or a substitute for human verification.
The request schema is published at /mps-audit-schema.json. Use a unique clientRequestId; reuse of the same value with different text returns 409. A completed response contains the audit result. A replay with the same request ID and passage returns the stored result without a second model invocation.
curl --request POST https://www.mahastrategies.com/api/mps-audits \
--header "Authorization: Bearer $MPS_AUDIT_CREDENTIAL" \ --header "Content-Type: application/json" \ --data '{ "clientRequestId": "example-audit-20260716-01", "text": "In 2024, the company reported a 32 percent increase in output." }'
/audit is the free, bounded public MPS preflight. It accepts a passage of up to 6,000 characters, returns a claim ma