Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Local-first, read-only ECZ-ID verifier over MCP (stdio): checks, reports, explains, routes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"ecz-id-verifier": {
"command": "npx",
"args": [
"-y",
"@ecocitizenz/ecz-id-mcp-verifier"
]
}
}
}在终端中运行这条命令
claude mcp add ecz-id-verifier -- npx -y @ecocitizenz/ecz-id-mcp-verifier粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"ecz-id-verifier": {
"command": "npx",
"args": [
"-y",
"@ecocitizenz/ecz-id-mcp-verifier"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"ecz-id-verifier": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ecocitizenz/ecz-id-mcp-verifier"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 Ecocitizenz 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.9.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Funooy Krillion Reference
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Funooy trivia references in six languages, with rules and fixed scoring. No daily spoilers.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Check public ECZ-ID Resolver posture from the CLI, CI or an MCP host. No sign-in, source upload or telemetry. Local policy decides.
A local-first, privacy-first tool that classifies a target, checks its public ECZ-ID Resolver posture where applicable, reports a deterministic result, explains it, and routes you onward. It only reads, reports, and routes — it never writes truth, activates proof, marks anything BOUND, performs checkout, or inspects artifact contents.
npx @ecocitizenz/ecz-id-mcp-verifier check --target ECZ-GB-A93K7Q
check is an accepted leading subcommand; --target does the work. Add --report for the human-readable soft report, --policy REQUIRE to fail closed when proof is missing, or --offline for classification and routing with no network call.
First useful result in under a minute: run the command above, read a real JSON result, and follow the routed next action. No sign-in, no account, no config. Install it with a plain
npm install @ecocitizenz/ecz-id-mcp-verifier; pin an exact version only when you need reproducibility (see Reproducible version pinning).
Real output for --target ECZ-GB-A93K7Q --policy OPEN --offline (representative excerpt; the full JSON also includes setup_handoff, request_to_resolve and additional boundary flags):
{
"schema_version": 1, "verifier": "ECZ-ID MCP Verifier", "verifier_version": "0.9.1", "target": "ECZ-GB-A93K7Q", "target_type": "ecz_id", "policy_mode": "OPEN", "result_state": "NO_PUBLIC_RESOLVER_PROOF_FOUND", "reason_codes": ["NO_PUBLIC_RESOLVER_PROOF_FOUND", "RESOLVER_READ_ONLY", "LOCAL_POLICY_DECIDES"], "resolver_url": "https://resolver.ecocitizenz.org/p/ECZ-GB-A93K7Q", "machine_json_url": null, "local_policy_decides": true, "recheck_before_reliance": true, "no_safety_or_approval_inference": true, "no_source_uploaded": true, "no_secrets_uploaded": true, "no_telemetry": true, "exit_code": 0 }
NO_PUBLIC_RESOLVER_PROOF_FOUND here means no public proof was located (offline run); it does not mean the target is unsafe. Local policy decides.
| Surface | How |
|---|---|
| CLI | npx @ecocitizenz/ecz-id-mcp-verifier check --target |
| CI / GitHub Action | uses: Ecocitizenz/ecz-id-mcp-verifier@v0.9.1 |
| MCP host | run the ecz-id-mcp-server stdio binary (three read-only tools) |
| Node library | import { verify } from "@ecocitizenz/ecz-id-mcp-verifier" |
Next actions: check a target · add to CI · add to an MCP host · inspect public Resolver proof · improve the posture of a target you operate · build an integration.
| You are… | Do this | You get |
|---|---|---|
| A developer checking a target | npx @ecocitizenz/ecz-id-mcp-verifier check --target | Deterministic classification + public Resolver posture, with routing. |
| A CI owner adding a gate | Add the GitHub Action with a policy, or run the CLI with --policy REQUIRE | A deterministic exit code + JSON/SARIF for your pipeline. |
| An MCP-host user | --print-mcp-config → paste into your host | Three read-only MCP tools over stdio. |
| A Node developer | import { verify } from "@ecocitizenz/ecz-id-mcp-verifier" | The canonical result contract in-process, no side effects. |
| A platform reviewer | --capabilities and inspect public Resolver posture | An honest, machine-readable statement of scope and limits. |
| An operator improving your own target | Follow the TrustOps route from the result | Guidance to improve the target's public Resolver posture. |
| A machine or agent | Read --capabilities and the canonical machine discovery pointer | Agent-readable capabilities and discovery, never treated as proof. |
The classifier is deterministic (regex only — no LLM, no network). A public Resolver lookup is performed only for a valid ECZ-ID; every other shape is classified and routed but not resolved, and no shape has its artifact contents, manifest, or runtime protocol inspected.
| Target shape | Example | Classified | Resolver lookup | Artifact / manifest / runtime inspected |
|---|---|---|---|---|
| ECZ-ID (parent) | ECZ-GB-A93K7Q | yes | yes (GET …/api/p/{parent}.json, online) | no / no / no |
| ECZ-ID (child) | ECZ-GB-A93K7Q::AGENT-4F9Q2A | yes | no (human URL only; no child machine endpoint) | no / no / no |
| MCP server URL | https://api.example.com/.well-known/ecz-mcp.json | yes | no (not directly resolvable) | no / no / no |
| Agent manifest URL | …/.well-known/ecz-agent.json | yes | no | no / no / no |
| API URL | https://api.example.com/... | yes | no | no / no / no |
| GitHub repo | https://github.com/org/repo | yes | no | no / no / no |
| npm package | left-pad or npm:left-pad | yes | no | no / no / no |
| PyPI package | pypi:requests | yes | no | no / no / no |
| Container image | ghcr.io/org/img@sha256:… | yes | no | no / no / no |
| Anything else | free text, whitespace, malformed ECZ-ID | classified unsupported_target | no | no / no / no |
For a non-ECZ-ID shape the verifier returns NO_PUBLIC_RESOLVER_PROOF_FOUND with resolver_url: null (it never fabricates a Resolver path). Classification is not security inspection.
ResultState and uppercase ReasonCodes.The verifier:
Network is opt-out via --offline / --no-network. No sign-in is required for normal checks. The public Resolver remains the proof surface; package and Registry metadata are discovery only, never proof.
Install from the public registry (this gives you the current release):
npm install @ecocitizenz/ecz-id-mcp-verifier
Or run it on demand without installing:
npx @ecocitizenz/ecz-id-mcp-verifier check --target ECZ-GB-A93K7Q
From source (contributors):
git clone https://github.com/Ecocitizenz/ecz-id-mcp-verifier.git
cd ecz-id-mcp-verifier npm install npm run build node dist/bin/cli.js --help
ecz-mcp-verify --target <value> [options]
Two equivalent command names are installed: ecz-id-mcp-verifier and ecz-mcp-verify (both run the same CLI). A third binary, ecz-id-mcp-server, starts the MCP stdio server.
| Flag | Default | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
--target | (required) | URL, package, repo, image, or ECZ-ID. | ||||||||
--target-type | auto | mcp_server \ | agent_manifest \ | api_url \ | github_repo \ | npm_package \ | pypi_package \ | container_image \ | ecz_id \ | auto |
--policy | OPEN | OPEN \ | PREFER \ | REQUIRE | ||||||
--operator | unknown | self \ | third_party \ | unknown (never auto-inferred). | ||||||
--json | on | Emit JSON output. | ||||||||
--report | off | Emit human-readable soft report. | ||||||||
--actions | off | Include action envelope in JSON output. | ||||||||
--resolver-base | https://resolver.ecocitizenz.org | Override resolver base. | ||||||||
--trustops-url | https://trustops.ecocitizenz.com/start | Override TrustOps URL. | ||||||||
--developer-base | https://developers.ecocitizenz.com | Override Developer Gateway. | ||||||||
--offline | off | Offline mode (no network). | ||||||||
--no-network | off | Same as --offline. | ||||||||
--timeout-ms | 10000 per attempt | Per-attempt lookup timeout (ms). Up to 3 attempts inside a 32 s total budget. Pinning it low can report a good record as unavailable when Core is cold. | ||||||||
--output | stdout | Write output to file. | ||||||||
--sarif | off | Also write a minimal SARIF 2.1.0 file. | ||||||||
--capabilities | Print the machine-readable capability profile (JSON) and exit. | |||||||||
--print-mcp-config | Print a ready-to-paste MCP host config (JSON) and exit. | |||||||||
--doctor | Run a local self-test (no network, no secret); add --report for human output. | |||||||||
--version | Print version and exit. | |||||||||
--help | Print help and exit. |
# Offline classification + JSON output
ecz-mcp-verify --target "ECZ-GB-A93K7Q" --offline
ecz-mcp-verify --target "https://api.example.com/.well-known/ecz-mcp.json" \ --policy REQUIRE --actions
ecz-mcp-verify --target "https://github.com/org/repo" --report
ecz-mcp-verify --target "ECZ-GB-A93K7Q" --output result.json --sarif result.sarif
Three deterministic, offline helpers make setup and integration fast — none require a target, a network call, or a secret:
# Confirm a healthy install (no network, no secret):
ecz-id-mcp-verifier --doctor
ecz-id-mcp-verifier --capabilities
ecz-id-mcp-verifier --print-
只显示了开头部分;其余内容请在仓库中阅读