ECZ-ID Developer Trust
One local trust layerfor both sides of the connection.
- See what MCP servers expose.
- See what agents can reach.
- Know what changed before they connect or act.
An MCP server is one half of the problem. The agent that calls it is the other. Developer Trust covers both, locally, before anything connects or acts: no account to run a check, no source, prompts, tool arguments, tool results or secret values uploaded, and no telemetry.
Choose your starting point
- I use MCPMCP Trust →What your MCP servers expose, and what changed.Free · Pro £12.99/month
- I use agentsAgent Trust →What your agents can reach, and how that reach changed.Free · Pro £12.99/month
- I need bothDeveloper Trust Pro →Both sides of the connection, one licence key.£19.99/month · £199/year
Both extensions are free forever, with no account. Install both free · Already purchased? Activate
Agent Trust · the caller
What can the caller reach?
- Agent configuration and manifests
- Declared tools and actions
- Credential-shaped key names, never values
- Agent and MCP relationships
- Change since the last scan
Connection
Local policy: ALLOW · WARN · REVIEW · BLOCK · QUARANTINE
Optional Local Trust Gate (Pro). Coverage is OBSERVED until it mediates; ENFORCED only for calls routed through it.
MCP Trust · the server
What does the server expose?
- MCP configuration in the workspace
- Declared tools and capabilities
- Credential-shaped key names, never values
- Remote endpoints, sanitised
- Trust Delta: what changed since your baseline
SeparatePublic proof is not local inspection. The Resolver (opens in a new tab) exposes published ECZ-ID state; nothing these extensions find creates or changes it.
Two extensions, one layer
A server is one half. The agent calling it is the other.
Each extension is free forever and useful on its own. Together they read the same connection from both ends.
ECZ-ID MCP Trust
What each MCP server is configured to do, which credential-shaped names it is handed, where it reaches, and what changed since your last scan.
MCP X-RAY - ECZ-ID MCP Trust Server: github Source ............ .vscode/mcp.json Transport ......... HTTP - declared Remote ............ https://api.example.com/mcp (credentials/query omitted) Environment keys .. 2 detected; 1 credential-shaped name Sandbox ........... not declared Fingerprint ....... a1b2c3d4e5f6 (local posture fingerprint) Change ............ unchanged since previous local scan Coverage: OBSERVED / UNMANAGED
- •MCP X-Ray
- •Supported configuration discovery
- •Trust Delta
- •Trusted baseline you control
ECZ-ID Agent Trust
What each agent declares, which MCP servers sit beside it, which credential-shaped names it is handed, and how that reach changed.
ECZ-ID Agent Trust - 2 agent surfaces - agent.yaml ........... no ecz-agent.json reference found yet - mcp tool config ...... resolver reference present Posture: neutral - local policy decides, re-check before reliance
- •Agent X-Ray
- •Declared tools and actions
- •Framework visibility
- •Workspace MCP relationships
Plans
Buy one side, or cover both for less.
Every plan below is optional. Both extensions are fully usable free, permanently, with no account.
Community
- •Both extensions, free forever
- •MCP X-Ray and Agent X-Ray
- •Credential-shaped name warnings
- •Trust Delta and change detection
- •Exportable local evidence reports
- •No account, no telemetry, no source or secrets uploaded
MCP Trust Pro
- •Trust Epochs
- •Advanced Tool X-Ray
- •Local Trust Gate (Protect This MCP)
- •Deterministic local policy inside the gate
- •Secret Shield
- •Remediation
Secure checkout by Shopify. Cancel any time. Already purchased? Activate here.
Agent Trust Pro
- •Authority Graph
- •Dangerous action chains
- •Authority Epochs
- •Reciprocal Agent ↔ MCP view
- •Remediation
Secure checkout by Shopify. Cancel any time. Already purchased? Activate here.
Developer Trust Pro
- •Everything in MCP Trust Pro and Agent Trust Pro
- •One licence key activates both extensions: paste the same key into each
- •One subscription instead of two
- •Less than the two Pro plans bought separately
Secure checkout by Shopify. Cancel any time. Already purchased? Activate here.
Two Pro plans bought separately are £12.99 + £12.99 per month. Developer Trust Pro is £19.99/month for both, on one licence key, with one renewal and one invoice.
ECZ-ID MCP Trust is published on both registries. Install free, in your editor or from the web.
ECZ-ID Agent Trust is published on both registries. Install free, in your editor or from the web.
Activate the licence from your order confirmation. A Developer Trust Pro bundle key turns on both extensions.
Activate your purchase →Free vs Pro
What a Pro licence actually adds.
Shown here for MCP Trust; Agent Trust follows the same shape, with the Authority Graph and action chains in place of the local gate.
| Capability | Community | MCP Trust Pro |
|---|---|---|
| MCP X-Ray: discovery and per-server inventory | Full | Full |
| Environment key NAMES + credential-shaped warnings | Full | Full |
| Sanitised remote endpoint and posture fingerprint | Full | Full |
| Trust Delta against a trusted baseline you control | Full | Full |
| Review Priority and Inspection Reason Codes | Full | Full |
| Privacy Proof, Inspection Receipt and exportable report | Full | Full |
| History of posture snapshots (Trust Epochs) | Trusted baseline | Full history, compare any two |
| Advanced Tool X-Ray (declared capability and schema) | — | Yes |
| Local Trust Gate with live mediation proof | — | Yes |
| Deterministic local policy inside the gate | — | Yes |
| Secret Shield (environment minimisation) | — | Yes |
| Remediation with diff, apply and rollback | — | Yes |
| No account to inspect, no telemetry, no source or secrets uploaded | Always | Always |
See the Agent Trust comparison →
These extensions review evidence and route you to it. They do not issue ECZ-ID proof, activate services, grant access, or make approval, safety, insurance or compliance decisions. Public proof lives in Resolver, and MCP Assurance is a separate, organisation-level product.
Free resource · 10 pages · no email required
The MCP & AI Agent Trust Preflight
Both sides of the connection in one checklist: 20 practical checks covering MCP transports and credential exposure, agent reach and capability chains, and the change review worth running before anything connects or acts. Vendor-neutral, and useful whether or not you install the extensions.
Runs with or without our extensions. Nothing to sign up for.
Questions
Choosing between them.
Which one do I need?
If you are wiring or reviewing MCP servers, start with MCP Trust. If you are granting tool access to an agent, start with Agent Trust. If you do both — and most people building with MCP end up doing both — the bundle covers both sides for less than the two singles.
What does the bundle actually give me?
Everything in MCP Trust Pro and Agent Trust Pro, under one subscription, with one licence key you paste into both extensions. It costs less than buying the two Pro plans separately.
Can I start free and upgrade later?
Yes, and that is the intended path. Install both free, run real scans on your own workspace, and buy Pro only once you know which side you need history and deeper analysis on.
Is the free version time-limited or a trial?
No. Community is free permanently and needs no account. Pro adds to Community; it never removes anything. If a Pro subscription lapses, only the Pro features deactivate and your locally retained history stays where it is.
Does any of my code or configuration get uploaded?
No. No source, prompts, tool arguments, tool results or secret values are uploaded, and there is no telemetry. Community makes no background outbound requests; links you choose open in your browser. If you start the Pro Local Trust Gate, it binds to 127.0.0.1 and talks only to the MCP upstream you already configured. Results carry names, counts, states and local fingerprints only.
Does it read my environment variable values?
Never. Environment variable NAMES are inventoried so you can review intended exposure; values are not read into results, displayed, retained or transmitted. The posture fingerprint is deliberately invariant to secret rotation.
I already paid. How do I turn Pro on?
Use the activation page and paste the licence from your order confirmation. The bundle licence activates both extensions. Activation is verified locally with asymmetric cryptography and the token is never displayed or transmitted.
Can I cancel?
Yes, at any time, from your account. Checkout and billing are handled by Shopify; this site runs no checkout of its own.
Free · no purchase needed
Operate an MCP server or an agent? Give it an ECZ-ID Passport.
The extensions inspect systems from the outside — the position you are in when you consume someone else's server or agent. If you operate one, you are on the other side of that question, and the people evaluating you want something they can check without asking you. An ECZ-ID Passport establishes a reusable identity with a public presence on the Resolver.
- Free, non-sellable, and needs only a DECLARED Parent
- A reusable machine-readable identity, not a one-off badge
- Public, read-only Resolver presence others can check
Passport issuance is an ECZ-ID platform service, not a function of the VS Code extensions. The extensions inspect and route; they never issue proof themselves.
The ECZ-ID estate
These extensions are one surface of a machine-trust infrastructure layer.
Identity, public proof and verifiable posture for the systems that now call each other without a human in the loop.