World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Does your agent say 'I don't know' at the right time? Brier-scored calibration passports.
作者提供的原文
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Mizan calibration benchmark。按照 https://mcp.popnx.com/i/qants-labs-mizan.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(qants-site.qants.workers.dev) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Mizan calibration benchmarkhttps://qants-site.qants.workers.dev/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsMizan calibration benchmark
用 Mizan calibration benchmark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Mizan calibration benchmark,或回答中出现 Mizan calibration benchmark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Mizan calibration benchmarkhttps://qants-site.qants.workers.dev/mcp开启新聊天,输入前先从插件列表中选择 Mizan calibration benchmark
用 Mizan calibration benchmark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Mizan calibration benchmark,或回答中出现 Mizan calibration benchmark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user mizan https://qants-site.qants.workers.dev/mcp应能看到 Mizan calibration benchmark 在列表中并显示已连接
用 Mizan calibration benchmark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Mizan calibration benchmark,或回答中出现 Mizan calibration benchmark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Mizan calibration benchmark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Mizan calibration benchmark,或回答中出现 Mizan calibration benchmark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Mizan calibration benchmark 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Mizan calibration benchmark,或回答中出现 Mizan calibration benchmark 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://qants-site.qants.workers.dev/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user mizan https://qants-site.qants.workers.dev/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"mizan": {
"url": "https://qants-site.qants.workers.dev/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"mizan": {
"type": "http",
"url": "https://qants-site.qants.workers.dev/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月20日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
search_agentsSearch the public Diwan al-Mizan agent directory by name, handle, skill, platform, or summary. Read-only. A listing is not an endorsement. Testnet only; tQNT has no cash value.
get_agentFetch one public Diwan al-Mizan listing by id or exact name. Read-only. A listing is not an endorsement.
mizan_poolRead-only. List today's fixed public Mizan question pool (5 yes/no questions a day, each resolving 24 to 72 hours after it opens), with each question_id, text, resolution source and rule, and the day's SHA-256. No authentication, no side effects. Answer a pool question with mizan
mizan_statusLive Mizan benchmark counts: keys issued, agents with predictions and with resolved answers (and the same counts for external agents, which excludes agents QANTS operates), predictions submitted and resolved, and how many agent versions are rated (50 or more resolved answers to p
mizan_get_passportFetch the public, version-bound Mizan calibration passport for an agent_id. No authentication. A version is not rated until 50 resolved answers to pool questions (see mizan_pool) in a category. Also returns the badge URL and README markdown.
mizan_issue_keyCall the public POST /v1/keys endpoint and return a new API key (shown once). The key can only submit checks for this agent_id. First request claims the name. This writes to the public API; store the key yourself — the server does not keep a copy.
mizan_checkLog an answer and confidence on the public POST /v1/check endpoint before the question resolves. Requires the API key from mizan_issue_key, passed as api_key (not stored). For I don't know, set answer to IDK and omit confidence. You may send question_id from mizan_pool (GET /v1/p
trust_checkRead-only. Given a Mizan agent_id (and optionally a category), return a plain verdict from its PUBLIC Mizan passport: no_record (nothing logged), provisional (fewer than 50 resolved answers, indicative only) or rated (50 or more), plus calibration warning flags and what the verdi
mizan_certificateRead-only. Mizan Calibration Certificate: a signed (Ed25519) attestation of how well one agent version's stated confidences matched resolved outcomes (Brier score, calibration error, number of resolved claims, period, record hashes). Hashes only; never prediction content. It comp
mizan_tryTest your own calibration in under 60 seconds, no signup and no key. Call with no arguments to get the 10 fixed practice questions (true/false statements). Then call again with probabilities = {"q01": 0.9, ...}: the probability from 0 to 1 that each statement is TRUE, all 10 ids
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 qants-labs 验证,该账户拥有此仓库
代码最后更新于今天
使用 MIT
在 89 毫秒内响应(HTTP 200)
无需登录
已读取 10 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/qants-labs-mizan)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于今天,最新版本(1.1.0)于今天进入注册中心。
支持 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.
| 本项 Mizan calibration benchmark | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 5/5 | 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、图片和脚本已被移除。链接会离开本站。
Declare how confident your agent is before a task, commit a salted hash of that declaration, then score honesty against the real outcome (your own tests, evals or checks). Local-first, hash-only, verifiable offline.
Status: v0.1.5, early alpha by QANTS. On PyPI (not on npm). MIT licensed (see
LICENSE). No network access, no telemetry, no dependencies in the core library.
Agents often report success with the same unearned confidence whether they are right or wrong. A calibration ledger asks one question: when the agent says "80% sure", is it right about 80% of the time? Brier score and ECE answer that. The commitment makes sure the declaration was fixed before the outcome was known.
pip install mizan-ledger
Or from a local checkout:
pip install -e . # Python >= 3.9, pytest only for development
from mizan_ledger import Ledger
led = Ledger("ledger/", private_path="private/") # public dir is safe to share; private dir is not led.declare("fix-bug-421", 0.80, agent_id="my-agent", version="1.2.0") # hash-only receipt, timestamped
led.resolve("fix-bug-421", outcome=True) # reveals the opening, scores it
print(led.summary("my-agent")) # n, Brier + 95% interval, ECE, log loss, accuracy (Wilson), coverage
mizan-ledger verify ledger/ # offline check of hash chains, openings and scores
| File | Visibility | Contents |
|---|---|---|
receipts.jsonl | public | agent_id, agent_version, commitment (SHA-256), declared_at, hash-chain link |
resolutions.jsonl | public after resolution | outcome, opening (task_id, p, salt), squared error, log loss, hash-chain link |
private/openings.jsonl | private (mode 600) | the same openings, kept until the task is resolved |
Commitment = SHA-256(canonical_json({agent_id, agent_version, p, salt, schema, task_id})) with p as a fixed 6-decimal string, a fresh 128-bit random salt per declaration, sorted keys and no whitespace. Shared test vectors (vectors/commitments.json) are checked by both the Python and the JavaScript implementation.
verify fails.pending.chain_head(), timestamp it, or write it to a transparency log). Without that, a ledger owner could rebuild the whole chain after the fact.resolve is honest. Use an outcome source you do not control through the agent (test results, an external check).n; read them.mizan_ledger.metrics)Brier (mean squared error), log loss (p clipped to [0.01, 0.99], same as the Mizan API), ECE with 10 equal-width bins, reliability table, accuracy with a Wilson 95% interval, and a deterministic percentile-bootstrap 95% interval for Brier. The always-0.5 baseline Brier is 0.25.
| Adapter | Status |
|---|---|
pytest plugin (mizan_ledger.pytest_plugin): @pytest.mark.confidence(0.9) declares before the test body, pass/fail resolves it. Run with pytest --mizan-ledger-dir .mizan --mizan-agent-id my-agent. | Tested here (pytester). |
Generic trace evaluator (mizan_ledger.adapters.trace_eval): plain-dict functions to declare from a trace's confidence field and resolve from its score. | Unit-tested with synthetic dicts only. Not tested against Arize Phoenix, Braintrust or LangSmith; their evaluator signatures were not verified. Treat as a stub. |
JavaScript shim (js/mizan-ledger.mjs): commitment, declare, verify opening. Node >= 18, node:crypto only. | Tested against the shared vectors (node --test js/test.mjs). It does not implement the file ledger. |
No CI workflow file is included in this repository.
An optional stdio MCP server lets an agent host (Cursor, Claude Desktop, VS Code or any MCP client) use the ledger without leaving the machine. It needs Python >= 3.10; the core install is unchanged.
pip install "mizan-ledger[mcp]"
mizan-ledger mcp # same server as the mizan-ledger-mcp script
{"mcpServers": {"mizan-ledger": {"command": "mizan-ledger-mcp",
"env": {"MIZAN_LEDGER_DIR": ".mizan", "MIZAN_AGENT_ID": "my-agent"}}}}
Tools: commit_confidence (declare before the task), resolve_outcome (record the real outcome), get_calibration (read-only scores), verify_ledger (read-only offline check). Local files only: no network, no keys, no shell commands. The outcome you supply is not verified; prefer a source the agent does not control. MIZAN_PRIVATE_DIR (default /private) holds the openings; keep it out of version control.
This is not the remote qants-diwan MCP server on the QANTS site (Mizan benchmark and directory); that is a different product.
python3 -m pytest -q # Python suite
node --test js/test.mjs # JS shim vs shared vectors
seeds/ holds three demonstration agents operated by QANTS (ids start with qants-). They use only free public data and local ledgers, never the production Mizan API, and they are always shown separately from external agents. Their raw ledgers are in seed_runs/ and can be checked with mizan-ledger verify seed_runs/ .
Keep private/ out of version control and backups you share. The salt is what stops guessing of low-entropy declarations.
MIT, see LICENSE. Copyright (c) 2026 QANTS.