npm
Available nowThe CLI and the local stdio MCP server. Local-first and read-only: it checks public Resolver posture and never writes truth.
npm install -g @ecocitizenz/ecz-id-mcp-verifier9 routes are available right now. Every one is read-only: it checks public ECZ-ID Resolver posture, reports a deterministic result, and routes. None of them writes truth, activates proof, or marks anything bound.
You do not need an ECZ-ID to verify one, and you do not need an account to read public proof.
ECZ-ID self-serve registration is temporarily unavailable. Public ECZ-ID verification — everything on this page — remains fully available. We would rather say so here than send you to a page that cannot complete.
Current published version: @ecocitizenz/ecz-id-mcp-verifier@0.9.0. The commands below are generated from that same value, so this page cannot fall behind the release.
The CLI and the local stdio MCP server. Local-first and read-only: it checks public Resolver posture and never writes truth.
npm install -g @ecocitizenz/ecz-id-mcp-verifierOne-off check with no global install. Useful in a scratch shell or a container.
npx -y @ecocitizenz/ecz-id-mcp-verifier --helpThe portable configuration. Any host that speaks MCP over stdio can launch the verifier this way.
{
"mcpServers": {
"ecz-id": {
"command": "npx",
"args": ["-y", "@ecocitizenz/ecz-id-mcp-verifier", "ecz-id-mcp-server"]
}
}
}Both ECZ-ID MCP surfaces are listed and current. Hosts that browse the Registry can discover them there.
io.github.Ecocitizenz/ecz-id-mcp-verifier 0.9.0 stdio
com.ecocitizenz/trust-mcp 0.2.0 streamable-httpThe hosted Streamable HTTP surface. Nothing to install — point an MCP client that supports remote servers at the endpoint. Read-only tools are anonymous; creating a Request-to-Resolve requires a Microsoft Entra bearer token.
https://trust-mcp.ecocitizenz.com/mcpRun the same deterministic check in CI. It reports a result and routes; it never writes truth, mutates the repository, or uploads source or secrets.
permissions:
contents: read
steps:
- uses: Ecocitizenz/ecz-id-mcp-verifier@v0.9.0
with:
target: ECZ-GB-RBS1NW
policy: PREFERThe Python family for ECZ-ID integration. These are libraries for building against ECZ-ID, not a second verifier.
pip install ecz-idPublic proof needs no client at all. Use the machine route for automation: it returns JSON on a match and HTTP 404 when no public record exists, so absence is unambiguous. The human page is client-rendered and is for people, not machines.
GET https://api.ecocitizenz.com/api/p/{ecz_id}.jsonAdd the verifier to Cursor by writing .cursor/mcp.json in your project, or ~/.cursor/mcp.json globally. Cursor install links are publisher-ungated: no account, no submission and no review stands between you and this configuration.
{
"mcpServers": {
"ecz-id": {
"command": "npx",
"args": ["-y", "@ecocitizenz/ecz-id-mcp-verifier", "ecz-id-mcp-server"]
}
}
}This configuration comes from the official Cursor documentation and the package is published, so the route is available to you today. We have not yet run an end-to-end interoperability test of the verifier inside Cursor, so we are not claiming tested compatibility — only that this is the correct, current way to add it.
These surfaces have no verified ECZ-ID install route today. Rather than publish a command that might fail, or claim compatibility we have not tested, each one says exactly what is missing.
ECZ-ID MCP Trust is published for VS Code, and VS Code can configure MCP servers.
We have not completed an end-to-end interoperability test of the verifier inside VS Code, so we make no claim that it works there. The portable stdio configuration above is the honest starting point. We will state otherwise only when we have a transcript.
Claude supports local MCP servers via configuration and remote MCP connectors.
The portable stdio configuration above applies, and the remote Trust MCP endpoint is live. No ECZ-ID connector-directory listing has been submitted, so we do not claim a directory install path.
A container image would let a host run the verifier without a local Node install.
Submission pending. No ECZ-ID image has been built, scanned or published, so there is no pull command to give you. We would rather show nothing than a command that fails.
A result of NO_PUBLIC_RESOLVER_PROOF_FOUND means no public ECZ-ID Resolver proof was found at the time checked. It does not mean the entity, agent, MCP or service is unsafe or untrustworthy. Re-check before reliance: how verification works.