Skip to content
EcoCitizenZ
Agent plugin · Privacy

ECZ-ID MCP Verifier

Privacy

This notice describes how the ECZ-ID MCP Verifier agent plugin — the package eczid-mcp-verifier, version 0.1.1 — handles information. It covers that plugin only.

This product behaves differently from the ECZ-ID evidence-review plugins, and this page does not repeat their language. Those plugins never touch the network. This one exists to read a public record, so where your host runs the Verifier server, requests do leave your machine. Exactly which ones, and what they carry, is set out below.

Applies to:
eczid-mcp-verifier 0.1.1
Effective date:
3 September 2026

Summary

  • The plugin's own files are a skill document and a server declaration. They contain no executable code, run nothing and send nothing.
  • Where your host launches the declared Verifier server, a check reads the public ECZ-ID Resolver and, for a URL or domain target, the public manifest that target itself publishes.
  • The one thing those requests carry about you is the target you asked about. Nothing about your workspace, your code or your conversation is sent.
  • No source code, no secrets, no prompts and no tool payloads are ever transmitted, and there is no hidden telemetry, analytics or usage counter.
  • In a host that does not run local MCP servers, nothing is launched and no request is made at all — see skills-only hosts.
  • The plugin writes nothing. It stores no cache, no history and no record of what you checked.
  • The agent host you run it in is a separate matter, governed by that platform's own terms — see your agent host.

Scope of this notice

This notice applies to the ECZ-ID MCP Verifier agent plugin, published by EcoCitizenz as eczid-mcp-verifier at version 0.1.1. The plugin consists of a manifest, one skill document, one MCP server declaration and its icons. It ships no review script and no server of its own.

It does not cover, and must not be read as covering:

  • the agent host or AI platform you run the plugin inside, which is operated by a third party under its own terms;
  • the ECZ-ID Verifier itself — @ecocitizenz/ecz-id-mcp-verifier@0.9.0 — which is a separately published package with its own repository and licence. What it does on the network when your host launches it is described here because you deserve to know, but the package is not part of this plugin;
  • the public ECZ-ID Resolver, TrustOps and other EcoCitizenz services, which are covered by the general EcoCitizenz Privacy Policy;
  • the other ECZ-ID plugins, which have their own notices. The evidence reviews make no network request at all.

What the plugin itself does

Nothing, on its own. Installed, the package places four kinds of file in your host: a manifest, a skill document written in Markdown, an mcp.json declaring one server, and two icons. None of it is a program. There is no review script here, and no code of ours runs when you install it.

The skill document is text the agent reads. The server declaration is a statement your host may act on. Everything that follows depends on whether your host acts on it.

When your host launches the Verifier server

A host that runs local stdio MCP servers reads the declaration and starts the server named ecz-id-verifier:

npx -y @ecocitizenz/ecz-id-mcp-verifier@0.9.0 ecz-id-mcp-server

The first launch downloads a package

npx is your package manager, not ours. On first use it fetches @ecocitizenz/ecz-id-mcp-verifier@0.9.0 and its dependencies from the npm registry and caches them on your machine. That is a network request to npm and a write to your npm cache, performed by your tooling under its own terms. If you would rather it did not happen at run time, install the package yourself in advance.

What a check sends, and where

The server runs locally on your machine and speaks to the agent over standard input and output. Its three tools are read-only:

  • ecz_check_target — Reads the public ECZ-ID Resolver, and where the target is a URL or a domain, the public manifest that target declares.
  • ecz_explain_result — Explains a result you already hold.
  • ecz_recheck_resolver — Reads the public ECZ-ID Resolver again.

A check therefore makes ordinary HTTPS requests to two kinds of destination, and no others:

  • The public ECZ-ID Resolver at https://resolver.ecocitizenz.org, which is operated by EcoCitizenz and is read-only: it publishes proof and cannot accept setup, checkout or directory queries.
  • The target's own public surface, where the target is a URL or a domain — the manifest it declares at a well-known address. That is a request to a third party you named, not to us.

What those requests carry about you is the target string you asked about, and the ordinary properties of any web request. They do not carry your workspace, your files, your prompts, the agent's replies or an account identifier, because the tools never receive any of those.

What EcoCitizenz sees

This is the honest difference between this plugin and the ECZ-ID evidence reviews, and it would be misleading to bury it. A review plugin sends us nothing. This one, when your host runs the server and you ask for a check, causes a request to reach a public EcoCitizenz surface, which sees that request as any web server sees one — the address it came from, the time, and what was requested, which includes the target.

That is a Resolver read, not a report about you: no account, no workspace, no content. What EcoCitizenz does with information received through its own services is governed by the general EcoCitizenz Privacy Policy, not by this plugin. If you would rather read the record without any client at all, the Resolver and the public machine descriptor are open in a browser.

Skills-only hosts: no server, no request

Some hosts accept skills but do not run local MCP servers, and some distributions of this plugin carry the skill directory alone. In that case the declaration is never acted on. No package is downloaded, no server starts, no tool exists and no request of any kind is made. The plugin is a document your agent has read.

What it can still do is explain: what the published ResultStates and ReasonCodes mean, what a result would and would not establish, and which public read-only surfaces you can open yourself. What it must not do is pretend. The skill is instructed never to simulate a tool result, never to guess a ResultState, and never to state that a target does or does not have public proof without a result actually obtained.

What is never transmitted

These hold in every host, on both routes. Neither the plugin nor the Verifier tools it declares transmit:

  • your source code, or the contents of any file in your workspace;
  • secrets, credentials, tokens or environment values;
  • your prompts, the agent's replies or tool payloads;
  • an account identifier, licence key or organisation name — none exists to send;
  • usage counts, timings, feature analytics or crash reports. There is no telemetry, hidden or otherwise.

Nor does anything inspect artifact contents: the check reads a public record about a target you named, not the target's code.

Storage and retention

The plugin stores nothing. It keeps no cache of results, no history of what you checked and no report file. A result exists as output in your agent session, and if you want to keep it you save it yourself.

The one thing that persists on your machine is the npm cache entry your package manager creates when it first downloads the Verifier package. That belongs to your tooling; clear it as you would any other cached package.

Because the plugin holds nothing, there is no plugin data for you to access, correct, export or delete. Requests about information held by EcoCitizenz services generally go through the EcoCitizenz Privacy Policy.

Secrets and credentials

The plugin never asks for a credential, has no field in which you could enter one, and needs none to run. The Resolver is public and read-only, so there is nothing to authenticate to and no token to hold.

Because it reads no file, it cannot read a secret value out of a .env file, a keystore or a configuration file. The only input a check takes is the target you type.

One consequence is worth stating plainly: the target you check is the thing that travels. If a hostname is itself sensitive, checking it sends that hostname to the Resolver and, for a URL target, to the host it names. You choose what to check.

Your agent host is a separate matter

This is the distinction that matters most, and we would rather over-explain it than let it be assumed.

What this notice covers

The plugin: what it contains, what it declares, and what a check sends — which is a read of the public Resolver and, for a URL or domain target, of that target's own public manifest.

Where your host does not run local MCP servers, that reduces to nothing at all: no server, no request.

What this notice does not cover

You run this plugin inside an agent host — a coding agent, an assistant, a CLI or an AI platform — operated by a third party. That platform decides what your conversation contains, what it transmits to its own servers, how long it retains it and what it does with it. That typically includes your prompts, the agent's replies, and the result the agent shows you, since the output becomes part of the conversation.

EcoCitizenz has no control over, and no visibility into, that processing. We do not operate those platforms, we are not a party to your agreement with them, and we cannot make commitments on their behalf. Their handling of your data is governed by their own privacy policy and terms, which you should read if that matters to you.

The practical point: choosing a local-first, read-only plugin does not by itself make your session private. It means this plugin adds no data flow of its own to whatever your platform already does.

Children

The plugin is a developer tool. It is not directed at children, and it collects no information about the person using it: it has no account, no identifier and no field in which a personal detail could be entered.

Changes to this notice

If the plugin's handling of information changes, this page is updated before or alongside the release that changes it, and the effective date is revised. Where the plugin is distributed through a marketplace listing, the updated notice is the one linked from that listing.

The version this notice applies to is stated at the top of the page. If you are running an older version, read the notice published with it.

Contact

Questions about this notice, or about privacy in relation to this plugin, can be sent to support@ecocitizenz.com. The same address is the route for data-protection requests under the general EcoCitizenz Privacy Policy.

See also the Support and Terms pages for this plugin, and the source if you would rather check than be told.

What this notice does not claim

  • Read-only and local-first is a description of behaviour, not a security guarantee. We do not claim the plugin is secure in any absolute sense, and no statement here is a security or compliance certification.
  • A ResultState is evidence about public proof. It does not certify, approve or guarantee any MCP server, agent, API, package, domain or business, and no public proof found is neutral rather than adverse.
  • The ECZ-ID Verifier server is published separately, with its own repository and licence. This notice describes what launching it does; the package's own documentation governs the package.
  • We describe what the plugin does. We make no representation about what your agent host, package manager, operating system or any other software on your machine does at the same time.

The plugin is open source. If you would rather check than be told, read SKILL.md and the Terms.

Publisher

ECZ-ID MCP Verifier is published by EcoCitizenz Ltd, trading as EcoCitizenz, company number 17348848, registered in England and Wales.

66 Paul StreetLondon EC2A 4NAUnited KingdomContact: support@ecocitizenz.com