World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Rounds of agent work under a brief: context to start, a check on each path, an audit at the end.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 22/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 34/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 spec-harness。按照 https://mcp.popnx.com/i/spec-family-spec-harness.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server spec-harness,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "spec-harness": { "command": "npx", "args": [ "-y", "@spec-family/spec-harness", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 spec-harness 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"spec-harness": {
"command": "npx",
"args": [
"-y",
"@spec-family/spec-harness",
"mcp"
]
}
}
}用 spec-harness 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 spec-harness,或回答中出现 spec-harness 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 spec-harness
spec-harness 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 spec-harness 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server spec-harness,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user spec-harness -- npx -y @spec-family/spec-harness mcp 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 spec-harness 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user spec-harness -- npx -y @spec-family/spec-harness mcp应能看到 spec-harness 在列表中并显示已连接
用 spec-harness 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 spec-harness,或回答中出现 spec-harness 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server spec-harness,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "spec-harness": { "command": "npx", "args": [ "-y", "@spec-family/spec-harness", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 spec-harness 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 spec-harness 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 spec-harness,或回答中出现 spec-harness 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server spec-harness,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "spec-harness": { "type": "stdio", "command": "npx", "args": [ "-y", "@spec-family/spec-harness", "mcp" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 spec-harness 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 spec-harness 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 spec-harness,或回答中出现 spec-harness 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user spec-harness -- npx -y @spec-family/spec-harness mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"spec-harness": {
"command": "npx",
"args": [
"-y",
"@spec-family/spec-harness",
"mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"spec-harness": {
"command": "npx",
"args": [
"-y",
"@spec-family/spec-harness",
"mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"spec-harness": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@spec-family/spec-harness",
"mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 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 账户 spec-family 验证,该账户拥有此仓库
代码最后更新于5天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 @spec-family/spec-harness@0.26.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/spec-family-spec-harness)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于5天前,最新版本(0.26.0)于5天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有: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.
| 本项 spec-harness | 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、图片和脚本已被移除。链接会离开本站。
Rounds of agent work under a brief a person approved: what the agent needs to start, a guard on the agent's writes, an escalation a person signs when the brief is not enough, and an audit when it ends.
spec-harness is the agent-facing member of the spec-\* tools. It calls no model and writes no content - the agent is the model. It gives the agent the contract and the facts, and answers, the same way every time, whether the agent stayed inside the lines. No runtime dependencies, no account, no network.
The family's words - brief, round, wave, ruling, premise, the two kinds of plugin - are defined in concepts, and the tutorial takes one round from the brief to the archive in ten steps. This README is the front page; the reference has every command, flag, hook, MCP tool, configuration key and doctor check.
npm install --save-dev @spec-family/spec-harness @spec-family/spec-brief
npx --no-install @spec-family/spec-harness init # the plan: what it would configure, and why npx --no-install @spec-family/spec-harness init --write # apply it
In a repository made with git init on main, with no remote yet, the plan reads:
run .spec-brief.json
spec-brief init: the brief and archive directories, every default spelled out update .spec-brief.json load spec-harness's plugin, "@spec-family/spec-harness/spec-brief-plugin": spec-brief's archive asks it whether a signed ruling allows a protected file, and refuses the file without it; measure the archive from main, as spec-harness does: without a base, spec-brief's archive warns that the scope went unmeasured and checks no protected file create .spec-harness.json rounds are measured from main, the branch init runs on: no remote records a default branch (refs/remotes/origin/HEAD); change "base" if rounds merge into another create .claude/settings.json the guard hooks, run with node from the project's install: a PreToolUse hook refuses writes to protected files; a PostToolUse hook warns about writes outside the scope; a SessionStart hook says, as a session starts, what would hold every write of it create .mcp.json the spec-harness MCP server, run with node from the project's install: start_round, check_path, request_escalation, audit_round, list_rounds advise .git/hooks/pre-commit no pre-commit hook runs spec-harness: one refuses a commit that changes what the active brief protects, for any agent or none, a shell's writes included; run spec-harness init --git-hook --write to add it advise .github/allowed_signers rulings count only when signed by a key listed here on the base branch: one line per person, namespaces="git" . Where an agent runs as the person, make it a FIDO2 key, ssh-keygen -t ed25519-sk, whose signature needs a touch no process can supply. Have the forge protect this file, the ADRs, the tool configurations and the CI configuration, so no change to them reaches the base branch without a person, and check each change in CI against the base branch's rules: on GitHub, CODEOWNERS and a protected branch; on GitLab Premium, Code Owners; on GitLab Free, a protected branch no one pushes to, merged by Maintainers, agents as Developers, and pipelines that must succeed. spec-core's docs/adopting.md has the settings
Nothing was changed. Run again with --write to apply the plan.
Then a brief: npx --no-install @spec-family/spec-brief new "Rotate tokens" scaffolds briefs/001_rotate-tokens.md, and a person fills it in and makes it active, here with affectedFiles: ["src/auth/**"] and protectedFiles: ["src/db/schema.ts"]. On its branch the guard answers for any path:
git switch -c brief/001-rotate-tokens
npx --no-install @spec-family/spec-harness guard src/db/schema.ts src/auth/token.ts README.md
refused brief 001 does not empower this round to change src/db/schema.ts (protectedFiles: src/db/schema.ts)
if the round cannot be done without it, stop and ask for a ruling: spec-harness escalate --path --reason , or the request_escalation tool ok src/auth/token.ts is in brief 001's scope (src/auth/) warning README.md is outside brief 001's scope, which covers src/auth/ if the round needs it, say so in briefs/001_rotate-tokens.md and add it to affectedFiles; the archive reports every file outside the scope that the round commits
That exits 1. Claude Code asks the same before every Edit and Write, through the hook init wrote, and the refused write never happens; Claude reads why, and the next step:
{"hookSpecificOutput":{"hookEventName":"PreToolUse","permissionDecision":"deny","permissionDecisionReason":"spec-harness: brief 001 does not empower this round to change src/db/schema.ts (protectedFiles: src/db/schema.ts). Next: if the round cannot be done without it, stop and ask for a ruling: spec-harness escalate --path <file> --reason <why>, or the request_escalation tool."}}
A repository that is not Node installs the tools the same way, from a package.json that holds { "private": true } (Installing).
The package is @spec-family/spec-harness, and the command it installs is spec-harness. The name without the scope is not this project: on npm, spec-harness is another publisher's package, and it installs a command of the same name. So give npx the full name:
npx --no-install @spec-family/spec-harness in a project that installed it runs that install, the version the lockfile pins, and where there is none it stops with an error that names this package. Every command in this README, in the reference and in the skills is written so.npx @spec-family/spec-harness, without --no-install, fetches this package where nothing is installed: for a look at --help, and little else.Never npx spec-harness, and not npx --no-install spec-harness either: npm still runs a copy of the other package that an earlier fetch left in its cache. Names has how to clear that cache, and the same for the siblings' names.
doctor checks the one on PATH.A sibling installed below its minimum is never run: doctor and every command that needed it name the minimum. Installing has why each release is the floor.
person approves brief 012 ─▶ agent on branch brief/012-rotate-tokens
│ spec-harness context ◀─┘ the brief, its scope, signed rulings, │ the rules in force, the documents it cites ▼ agent edits ── hook: protected? refused, with the next step │ outside the scope? a warning after the write │ ├── needs a protected file ─▶ escalate ─▶ person rules, signs ▼ spec-harness audit ─▶ spec-brief archive --dry-run ─▶ person archives
The round's brief is named, never guessed: --brief , then SPEC_BRIEF, then the branch, brief/{id}, brief-{id}, */brief/{id} or */brief-{id}, so claude/brief-042-rotate-tokens is brief 042. A name that names no brief is not passed over for the next. A round has the order in full, the branch a forge's CI names on a detached HEAD, worktrees and the branches an app makes, and what each layer catches of a session that writes through a shell.
In the order a round meets them; init and doctor set a repository up and check it. Each heading's page in the reference has the whole of it.
context [brief]The packet an agent starts a round with: the brief in full - it is the contract - then the files it may write and must not change, the rulings already signed, the briefs it depends on, the architecture rules spec-guard holds over its scope, and the documents it cites, whole, up to a budget. What could not be read is named, never left out (context).
guard and the hooksMay the round write this?
| The path | The answer |
|---|---|
| one the brief protects | Refused, unless a signed ruling allows it. |
one in affectedFiles | Allowed. |
| anything else | Outside the scope: a warning by default, or a question to the person, or a refusal (outOfScope: warn, ask, deny). |
The hooks ask it of every write:
| When | The hook | What it does |
|---|---|---|
Before an Edit, Write, MultiEdit or NotebookEdit | hook claude, Claude Code's PreToolUse | Refuses a write to a protected file, with the reason and the next step. It never answers allow, which would skip the person's own permission prompt. |
| After such a write | hook claude, PostToolUse | Warns Claude of a write outside the scope. |
| As a session starts | hook claude, SessionStart | Says in one line what would hold every write of the session. It holds nothing. |
As a turn ends, with "turnReport": true | hook claude, Stop | Reports every changed path the brief protects or that is outside its scope, a shell's writes among them. |
Before Codex's apply_patch, or a shell command that hands it a patch | hook codex, Codex's PreToolUse, from .codex/hooks.json | Refuses a write to a protected file, with the reason and the next step. |
| Before Copilot creates or edits a file | hook copilot, Copilot's preToolUse, from .github/hooks/spec-harness.json | The same, as Copilot reads it. |
| Before a commit | hook git, git's pre-commit, from init --git-hook | Refuses a commit that changes a protected file, for any agent or none. |
A guard is a guardrail - an agent that writes through a shell passes it - so the audit and spec-brief's archive are the gates (guard and the hooks).
The write guard covers Claude Code, and Codex and Copilot by their documentation. hook codex and hook copilot answer each agent in its own language, as its hooks reference describes it (read 2026-11-12), and are tested against the shapes it documents; neither agent was run against them. Other agents have hooks that can hold a write, each in a language of its own. By their documentation, GitHub Copilot and Cursor also read .claude/settings.json and run the line init wrote there, and neither reads its answer: Copilot would hold every edit, whatever hook copilot answers, and Cursor let every one through. hook claude says so in one line where the question carries another agent's fields, and checks nothing for it. For any agent, git's pre-commit hook from init --git-hook, the audit and spec-brief's archive hold.
escalate, rule, rulingsWhen the round cannot be done without a protected file, the agent writes a memo and stops; a person rules, and signs:
# the agent
npx --no-install @spec-family/spec-harness escalate --path src/db/schema.ts \ --reason "Rotation needs a rotated_at column." \ --option "Allow: one additive column" --option "Refuse: rotation keeps no timestamp" \