ECZ-ID MCP Trust

Start here

1. Product home: https://mcp.ecocitizenz.com/
2. Developer quickstart / docs: https://developers.ecocitizenz.com/quickstarts/mcp/
3. Resolver — public proof: https://resolver.ecocitizenz.org
4. TrustOps — free Passport / setup / operating services: https://trustops.ecocitizenz.com/start
5. Machine discovery: https://machine.ecocitizenz.org/.well-known/ecz-machine.json

Start with the specialist product home for the complete product journey. Use Developer Gateway for implementation, Resolver for public proof, TrustOps for free Passport/setup/operating services, and machine discovery for canonical machine-readable routing.

What changed since you last trusted this?

MCP configuration changes. Endpoints move, tools change, schemas expand and credential-shaped environment key names appear. ECZ-ID MCP Trust keeps the reference point under your control and shows what changed against it.

Free local review. No account is required for the local check, and secret values, prompts, tool arguments and tool results are never displayed or transmitted.

Useful for

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

What you can do in under a minute

1. Open a trusted workspace containing MCP configuration.
2. Run ECZ-ID MCP Trust: Check MCP Trust.
3. Review MCP X-Ray, Trust Delta, current proof posture and privacy facts.
4. Resolve existing proof, request current proof, or create/connect a free MCP Passport when you operate the server.

Community — free local review

Community includes:

• MCP X-Ray — privacy-filtered local server inventory;
• Trust Delta — NEW / CHANGED / UNCHANGED / REMOVED against the trusted baseline you control;
• stable MCP Trust Inspection Reason Codes;
• Privacy Proof and privacy-preserving Inspection Receipts;
• Resolver lookup and current-proof routes;
• free MCP Passport acquisition.

The MCP Passport is the durable core identity. It is free and is not replaced or metered by a software subscription.

MCP Trust Inspection Reason Codes

The inspection vocabulary is versioned under namespace eczid.mcp-trust.inspection.v1.

MCP Trust Inspection Reason Codes describe local configuration and change observations. They are distinct from canonical ECZ-ID Resolver/Verifier ReasonCodes carried with ResultStates and Action Envelopes.

Common codes you may see include:

• MCP_ADDED — a server appears in the current local inspection but not the trusted baseline;
• REMOTE_ENDPOINT_CHANGED — the privacy-filtered remote endpoint projection changed;
• CREDENTIAL_SHAPED_ENV_KEY — a credential-shaped environment-variable name was observed; secret values are excluded;
• NO_PUBLIC_RESOLVER_PROOF_FOUND — the requested public Resolver evidence was not established by the observation;
• BASELINE_NOT_ESTABLISHED — no trusted local comparison baseline has yet been established.

NO_PUBLIC_RESOLVER_PROOF_FOUND shares its name with a canonical ECZ-ID ResultState; within this inspection namespace it is a local inspection observation, not a Resolver result and not a canonical ECZ-ID ResultState.

Trust Delta

Every check compares current observable MCP configuration with the baseline you last accepted:

The baseline moves only when you explicitly establish it. Scanning twice does not silently absorb a change.

Coverage truth

Inspection alone can never produce ENFORCED.

MCP Trust Pro — optional paid local developer software

MCP Trust Pro adds runtime-aware local protection without changing the free MCP Passport identity:

• Protect This MCP through the Local Trust Gate for supported transports;
• Secret Shield using environment key-name controls without displaying secret values;
• Trust Epochs for retained local history and comparison;
• Advanced Tool X-Ray for capability-class and material-change indicators;
• deterministic local ALLOW / WARN / REVIEW / BLOCK / QUARANTINE policy;
• reviewable remediation with preview, backup and rollback.

MCP Trust Pro is a Developer Trust software entitlement. It does not issue or alter Resolver proof, and it does not replace or meter the free MCP Passport.

Developer Trust Pro Bundle unlocks both MCP Trust Pro and Agent Trust Pro.

Separate organisational product: MCP Assurance

Organization-level MCP Assurance is a separate product, and Resolver public proof stays separate from local policy. MCP Assurance may be relevant when an organisation needs higher-level ongoing MCP assurance, but it is not an alias for the MCP Trust Pro entitlement.

Public Trust MCP

The extension can open VS Code's own MCP installer for the canonical public endpoint:

https://trust-mcp.ecocitizenz.com/mcp

VS Code still owns the server-trust decision and tool approvals. ECZ-ID does not silently trust or start the server.

Result semantics

Review Priority and reason codes describe observed local evidence. They are not a safety, approval or compliance determination, and they are not a guarantee. Missing public Resolver proof means the requested public evidence was not established; it does not by itself determine whether an MCP server should be relied upon.

Privacy & Workspace Trust

Free identity vs optional products

Payment for Developer Trust software never creates, replaces or meters the underlying MCP Passport identity.

Frequently asked questions

Does installing this extension create an ECZ-ID?
No. Local review works without an account. Creating or connecting a free MCP Passport is a separate explicit action.

Does MCP Trust Pro replace the MCP Passport?
No. The Passport remains the durable identity. MCP Trust Pro is optional local developer software.

Is MCP Assurance the same product as MCP Trust Pro?
No. Organization-level MCP Assurance is separate. MCP Trust Pro is the local Developer Trust software entitlement used by this extension.

What does Developer Trust Pro Bundle do?
It unlocks both MCP Trust Pro and Agent Trust Pro under the established Developer Trust entitlement model.

Does a missing proof reference mean the MCP server is unsafe?
No. It means the requested resolver-verifiable evidence was not established by the observation. Local policy decides whether the evidence you review is sufficient.

When is coverage ENFORCED?
Only while traffic is genuinely mediated by a live Local Trust Gate and its mediation proof remains current.

Does the extension expose secret values in receipts or fingerprints?
No. The evidence projection uses names, counts, states and digests; secret values are excluded.

Machine-readable facts

This table is a stable human-readable index into ECZ-ID's real machine interfaces; it is not a substitute for the canonical machine-discovery document.

Canonical machine discovery is authoritative for machine routing and supported interfaces. Local extension observations, Resolver public proof and paid operating services remain separate layers.

Product resources

1. Product home: https://mcp.ecocitizenz.com/
2. Developer quickstart / docs: https://developers.ecocitizenz.com/quickstarts/mcp/
3. Resolver — public proof: https://resolver.ecocitizenz.org
4. TrustOps — free Passport / setup / operating services: https://trustops.ecocitizenz.com/start
5. Machine discovery: https://machine.ecocitizenz.org/.well-known/ecz-machine.json
6. Support: https://www.ecocitizenz.com/pages/contact

Local extension observations, public proof and operating setup are separate layers. Use the specialist home for the product journey, the Developer Gateway for implementation, Resolver for public proof and the canonical machine-discovery endpoint for machine-readable routing.