ECZ-ID MCP Trust

Inspect MCP configuration and resolver-reference posture locally.

Free, local-first. No source upload. No sign-in to run a check.

• Detects mcp.json, .vscode/mcp.json, claude_desktop_config.json, ecz-mcp.json.
• Plain-English posture for detected MCP servers and clients.
• One click to Resolver re-check and supported MCP setup.

Useful for

Useful across many legitimate roles. Commonly used by:

• MCP server and client developers
• AI tooling and platform teams
• Security reviewers of MCP integrations
• Architects standardising MCP across a fleet

Relevant when you are adding or reviewing an MCP server, before relying on an MCP integration, an evaluator asks which servers carry public proof.

What you can do in under a minute

1. Open or scan the workspace — run ECZ-ID MCP Trust: Check MCP Trust.
2. Review findings in plain English — grouped, with neutral posture.
3. Open Resolver guidance or continue supported setup where relevant.

What it looks for

• MCP server configuration (mcp.json, .vscode/mcp.json, mcp.config.*).
• Known MCP client configs (e.g. claude_desktop_config.json).
• An ecz-mcp.json / .well-known/ecz-mcp.json resolver reference.
• Whether a resolver-verifiable proof reference is missing for a detected server.

Example result

ECZ-ID MCP Trust  -  2 MCP configs
- mcp.json ............. server detected, no proof reference yet
- .vscode/mcp.json ..... resolver reference present
Posture: neutral - re-check before reliance

What results mean

Results describe public-proof posture, never a safety, approval, certification or compliance verdict:

resolvable · partial public proof · no public proof reference found yet · review recommended · re-check before reliance · your local policy decides.

There is no “pass/fail”. Local policy decides what is sufficient, and you should re-check before reliance.

Recommended next steps

• Inspect the finding — plain-English detail, no verdict.
• Copy verification guidance — a claim-free snippet you can share.
• Open Resolver — read-only public proof lookup.
• Continue supported setup — hand off to TrustOps (metadata only).
• Open documentation — Developer Gateway.
• Re-check later — re-run before you rely on a result.

Privacy & permissions

See the bundled PRIVACY.md for the full notice.

Frequently asked questions

Is this extension free?

Yes. Every local check is free — you never need to sign in or pay to run one.

Does it upload my source code?

No. No source, prompts, secrets or tool payloads ever leave your device, and there is no telemetry.

Does it read my file contents?

It reads filenames and paths during a scan. It only reads the contents of a file you explicitly ask it to inspect (for example an ecz-*.json you choose to validate).

Does a missing proof reference mean something is unsafe?

No. “No public proof reference found yet” is neutral — it is not a verdict of “unsafe”. It only means resolver-verifiable public proof was not detected.

What does Resolver do?

Resolver is a read-only public proof lookup. The extension can open it so you can check public proof yourself; the extension never writes, activates or decides anything.

Do I need an ECZ-ID before using the extension?

No. You can run every local check without one. An ECZ-ID is only relevant if you later choose supported setup in TrustOps.

What happens when I continue supported setup?

The extension hands off to TrustOps with metadata only. It runs no checkout itself; TrustOps handles acquisition, setup and lifecycle.

Can this extension make a compliance or approval decision?

No. It surfaces posture and routes you to proof. Local policy decides sufficiency; it never certifies, approves or guarantees.

Which MCP configuration files can it detect?

mcp.json, .vscode/mcp.json and ecz-mcp.json.

Is MCP Registry presence treated as proof?

No. Registry presence is not treated as resolver-verifiable public proof. Re-check before reliance.

Does this create or host an MCP server?

No. It only inspects local configuration and resolver-reference posture. It never creates, hosts or runs a server.

What it does not do

• No source / prompt / secret upload, and no telemetry.
• Provides local evidence review and guidance only - it does not issue ECZ-ID proof, activate services, grant access, or make approval, safety, insurance or compliance decisions.
• Makes no safety, approval, certification or compliance claim. Registry presence is not proof, and this extension makes no remote-runtime claim. Resolver is the only public proof surface.
• Runs no checkout or payment — commercial actions happen only in TrustOps.

Install & first use

1. In your editor's Extensions view, search for ECZ-ID MCP Trust (publisher EcoCitizenz) and install it.
2. Open a project and trust the workspace.
3. Run ECZ-ID MCP Trust: Check MCP Trust and review the grouped findings.

Free vs supported setup

• Free, local-first: detected MCP configuration with posture, missing-proof findings, and Resolver re-check / supported-setup routes — no sign-in and no purchase to run a check.
• Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for MCP server identity and public proof — relevant when you need a resolver-verifiable result others can check, not just local review.
• You never need to buy anything to get local value; supported setup is a separate, optional step handled entirely in TrustOps.

Python / CLI

Prefer Python, CI or terminal automation?

python -m pip install ecz-id-mcp
ecz-id-mcp --help

• Open the matching Python package: https://pypi.org/project/ecz-id-mcp/
• Explore all 10 ECZ-ID Python tools: https://developers.ecocitizenz.com/python

The Python tools run locally and inspect, explain and route only — the same role boundary as this extension. They do not issue an ECZ-ID, create public proof or replace Resolver proof.

Machine-readable facts

Need help choosing the right ECZ-ID route?

Use ECZ-ID GPT guidance: https://trustops.ecocitizenz.com/start#gpt-guidance

Route guidance only. TrustOps handles setup; Backend/Core writes truth; Resolver proves public state. Local policy decides reliance. Re-check before reliance.

Links & support

• Resolver (read-only proof): https://resolver.ecocitizenz.org
• TrustOps (supported setup): https://trustops.ecocitizenz.com/start
• Developer Gateway (docs & support): https://developers.ecocitizenz.com
• Privacy: see the bundled PRIVACY.md file

ECZ-ID is independent trust infrastructure. Third-party names describe compatible ecosystems only and do not imply endorsement or affiliation. Local policy decides whether the evidence you review is sufficient.