Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Ecz Id MCP Verifier

by Ecocitizenzversion 0.9.0i★ –iRuns on your computer
Registry nameio.github.Ecocitizenz/ecz-id-mcp-verifier

Install

Overview

Description from the maker (original English)

Local-first, read-only ECZ-ID verifier over MCP (stdio): checks, reports, explains, routes.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

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-verifier

Open in Cursor

Or copy the settings yourself

Paste 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.

Open in VS Code

Or copy the settings yourself

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.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Ecocitizenz, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18354 servers in this category
  • Published to the registry more recently than 30% of the other 18354 servers in this category
  • Basic checks equal to or better than 100% of the other 18354 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ecz Id MCP Verifier safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Qemu MCP

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Qemu MCP

by 0xmortuex

Boot and drive QEMU VMs from an AI agent: keys, screenshots, serial. No guest agent.

Runs on your computerUpdated today
Install

README from the maker

Open the README

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.

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-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).

Representative result

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.

Use it from

SurfaceHow
CLInpx @ecocitizenz/ecz-id-mcp-verifier check --target
CI / GitHub Actionuses: Ecocitizenz/ecz-id-mcp-verifier@v0.9.1
MCP hostrun the ecz-id-mcp-server stdio binary (three read-only tools)
Node libraryimport { 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.

Common workflows

You are…Do thisYou get
A developer checking a targetnpx @ecocitizenz/ecz-id-mcp-verifier check --target Deterministic classification + public Resolver posture, with routing.
A CI owner adding a gateAdd the GitHub Action with a policy, or run the CLI with --policy REQUIREA deterministic exit code + JSON/SARIF for your pipeline.
An MCP-host user--print-mcp-config → paste into your hostThree read-only MCP tools over stdio.
A Node developerimport { verify } from "@ecocitizenz/ecz-id-mcp-verifier"The canonical result contract in-process, no side effects.
A platform reviewer--capabilities and inspect public Resolver postureAn honest, machine-readable statement of scope and limits.
An operator improving your own targetFollow the TrustOps route from the resultGuidance to improve the target's public Resolver posture.
A machine or agentRead --capabilities and the canonical machine discovery pointerAgent-readable capabilities and discovery, never treated as proof.

Supported target shapes

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 shapeExampleClassifiedResolver lookupArtifact / manifest / runtime inspected
ECZ-ID (parent)ECZ-GB-A93K7Qyesyes (GET …/api/p/{parent}.json, online)no / no / no
ECZ-ID (child)ECZ-GB-A93K7Q::AGENT-4F9Q2Ayesno (human URL only; no child machine endpoint)no / no / no
MCP server URLhttps://api.example.com/.well-known/ecz-mcp.jsonyesno (not directly resolvable)no / no / no
Agent manifest URL…/.well-known/ecz-agent.jsonyesnono / no / no
API URLhttps://api.example.com/...yesnono / no / no
GitHub repohttps://github.com/org/repoyesnono / no / no
npm packageleft-pad or npm:left-padyesnono / no / no
PyPI packagepypi:requestsyesnono / no / no
Container imageghcr.io/org/img@sha256:…yesnono / no / no
Anything elsefree text, whitespace, malformed ECZ-IDclassified unsupported_targetnono / 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.

What this package does

  • Classifies a target deterministically (no LLM).
  • For a valid ECZ-ID, GETs the public Resolver machine projection (read-only) and reports its posture.
  • Reports a canonical ResultState and uppercase ReasonCodes.
  • Emits JSON, an optional human-readable soft report, an optional local Action Envelope (routing-only metadata), and an optional SARIF 2.1.0 file.
  • Exposes deterministic exit codes for CI integration.
  • Ships a GitHub Action wrapper and a read-only MCP stdio server.

What this package does not do

  • It does not write truth.
  • It does not activate proof.
  • It does not mark anything BOUND.
  • It does not inspect artifact contents, manifests, or runtime protocol of any target.
  • It does not certify the safety of any server, agent, product, or API.
  • It does not approve agents.
  • It does not decide global trust.
  • It does not upload source code.
  • It does not upload secrets, API keys, prompts, or tool payloads.
  • It does not emit telemetry, analytics, Sentry, or PostHog beacons.
  • It does not call Backend/Core.
  • It does not write to the Resolver.
  • It does not call TrustOps as a verifier backend.
  • It does not perform checkout.
  • It does not create a client-side trust badge.
  • It does not issue a reusable trust credential.
  • It does not treat npm or Official MCP Registry presence as ECZ-ID proof.
  • It does not infer safety or approval state for any third party.
  • It does not run autonomous LLM or agent behaviour.

Privacy

The verifier:

  • no source upload,
  • no secrets upload (no API keys, no environment variables),
  • never uploads prompts or tool payloads,
  • never uploads private logs or raw telemetry,
  • never uploads customer data,
  • never sends a body to the Resolver (GET-only),
  • never sends private headers,
  • never emits analytics, Sentry, or PostHog beacons,
  • never phones home,
  • never auto-updates.

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

Install from the public registry (this gives you the current release):

npm install @ecocitizenz/ecz-id-mcp-verifier

or global: npm install -g @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

CLI

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.

Options
FlagDefaultDescription
--target(required)URL, package, repo, image, or ECZ-ID.
--target-typeautomcp_server \agent_manifest \api_url \github_repo \npm_package \pypi_package \container_image \ecz_id \auto
--policyOPENOPEN \PREFER \REQUIRE
--operatorunknownself \third_party \unknown (never auto-inferred).
--jsononEmit JSON output.
--reportoffEmit human-readable soft report.
--actionsoffInclude action envelope in JSON output.
--resolver-basehttps://resolver.ecocitizenz.orgOverride resolver base.
--trustops-urlhttps://trustops.ecocitizenz.com/startOverride TrustOps URL.
--developer-basehttps://developers.ecocitizenz.comOverride Developer Gateway.
--offlineoffOffline mode (no network).
--no-networkoffSame as --offline.
--timeout-ms10000 per attemptPer-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 stdoutWrite output to file.
--sarif offAlso write a minimal SARIF 2.1.0 file.
--capabilitiesPrint the machine-readable capability profile (JSON) and exit.
--print-mcp-configPrint a ready-to-paste MCP host config (JSON) and exit.
--doctorRun a local self-test (no network, no secret); add --report for human output.
--versionPrint version and exit.
--helpPrint help and exit.
CLI examples
# Offline classification + JSON output

ecz-mcp-verify --target "ECZ-GB-A93K7Q" --offline

REQUIRE policy with action envelope

ecz-mcp-verify --target "https://api.example.com/.well-known/ecz-mcp.json" \ --policy REQUIRE --actions

Human-readable soft report

ecz-mcp-verify --target "https://github.com/org/repo" --report

Write JSON + SARIF files for CI

ecz-mcp-verify --target "ECZ-GB-A93K7Q" --output result.json --sarif result.sarif

Self-test, capabilities, and MCP config

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

Print the machine-readable capability profile (what it does and does not do):

ecz-id-mcp-verifier --capabilities

Print a ready-to-paste MCP host configuration:

ecz-id-mcp-verifier --print-

Only the beginning is shown; read the rest in the repo

Ask PopNx