Ecz Id Verifier MCP server
io.github.Ecocitizenz/ecz-id-mcp-verifier·v0.9.0Local-first, read-only ECZ-ID verifier over MCP (stdio): checks, reports, explains, routes.
0 stars84 downloads/wk
Reviews
Write oneNobody has reviewed Ecz Id Verifier yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Ecz Id Verifier tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
ecz_check_targetRead-only. Returns the canonical ECZ-ID verifier result contract for a target (result_state, reason_codes, routing, and read-only boundary flags). Does not write truth, activate proof, mark BOUND, or decide global allow/deny. Local policy decides.
ecz_explain_resultRead-only. Returns public-safe explanations for existing canonical result_state and reason_codes. Invents no new states or codes and emits no global allow/deny decision.
ecz_recheck_resolverRead-only public Resolver re-check using the canonical Resolver client (GET only). Returns the current public proof projection with recheck_before_reliance. Never writes truth or activates proof.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- Code scan53 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 37 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How Ecz Id Verifier compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 84
- more than 59% of 12,191 servers with a package
What its tools let an agent do: 3 read
Install Ecz Id Verifier in Claude Code, Cursor or VS Code
Runs npx -y @ecocitizenz/ecz-id-mcp-verifier on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add ecz-id-mcp-verifier -- npx -y @ecocitizenz/ecz-id-mcp-verifier
What the publisher says
From the Ecz Id Verifier repository's README, as published. We do not edit it. Read it on GitHub
ECZ-ID MCP Verifier(TM)
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.
Quick start
npx @ecocitizenz/ecz-id-mcp-verifier check --target ECZ-GB-A93K7Qcheck 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).
Representative result
Real output for --target ECZ-GB-A93K7Q --policy OPEN --offline (representative excerpt; the full JSON also includes setuphandoff, requestto_resolve and additional boundary flags):
{
"schema_version": 1,
"verifier": "ECZ-ID MCP Verifier",
"verifier_version": "0.9.0",
"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
}NOPUBLICRESOLVERPROOFFOUND here means no public proof was located (offline run); it does not mean the target is unsafe. Local policy decides.
Use it from
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.
Common workflows
Supported target shapes
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Ecz Id Verifier: common questions
- Is Ecz Id Verifier MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Ecz Id Verifier safety report
- How do I install Ecz Id Verifier?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Ecz Id Verifier need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Ecz Id Verifier maintained?
- The last commit was 42 days ago (2026-09-23). The latest release is v0.9.0.
- What can I use instead of Ecz Id Verifier?
- Servers from other publishers that do the same job: MCP for Adobe Premiere Pro MCP server.
- How does Ecz Id Verifier compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Ecz Id Verifier
Same job from other publishers: the closest match first, then the best rated.
- MCP for Adobe Premiere ProLocal-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check.not reviewedEstablishedA