Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Local-first, read-only ECZ-ID verifier over MCP (stdio): checks, reports, explains, routes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ecz-id-verifier": {
"command": "npx",
"args": [
"-y",
"@ecocitizenz/ecz-id-mcp-verifier"
]
}
}
}Run this in your terminal
claude mcp add ecz-id-verifier -- npx -y @ecocitizenz/ecz-id-mcp-verifierPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ecz-id-verifier": {
"command": "npx",
"args": [
"-y",
"@ecocitizenz/ecz-id-mcp-verifier"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ecz-id-verifier": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ecocitizenz/ecz-id-mcp-verifier"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Ecocitizenz, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Qemu MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Boot and drive QEMU VMs from an AI agent: keys, screenshots, serial. No guest agent.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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-
Only the beginning is shown; read the rest in the repo