ECZ-ID Agent Trust

See what your agent can reach before you let it act.

Free, local-first visibility into declared agent surfaces, tools, capability relationships, credential-shaped environment key names and workspace MCP relationships. No account. No telemetry.

Community free forever. Pro when you need more.

One extension. Community stays free. Pro unlocks in place.

Agent Trust Community Free forever

• Agent X-Ray and local agent-surface inventory
• declared tool and capability visibility
• credential-shaped environment key-name warnings
• workspace MCP relationships
• local change detection
• Resolver/operator lookup
• no paid account required

Agent Trust Pro £12.99/month or £119/year

Everything in Community, plus:

• Authority Graph deterministic evidence-backed authority relationships
• Authority Epochs retained local authority history and change comparison
• dangerous action-chain indicators for human review
• reachability analysis
• credential-key exposure review
• reciprocal Agent-to-MCP view
• reviewable remediation

Explore Agent Trust Pro ->

Need Agent + MCP? Explore Developer Trust Pro ->
Agent Trust Pro + MCP Trust Pro under one Developer Trust entitlement £19.99/month or £199/year.

Already purchased? Activate Pro ->

The Marketplace download is free because Community is free forever. Pro is an optional entitlement that unlocks additional capabilities in this same extension.

Community and Pro

Community (free, no sign-in) is everything above: agent-surface detection, Agent X-Ray, change detection, and Resolver / supported-setup routes.

Agent Trust Pro adds a deeper, evidence-only view of what your agents can reach, all computed locally:

• Authority Graph - a graph of agents, tools, MCP targets, APIs, credential key NAMES, declared permissions and capability signals. Every node and edge is derived from discovered evidence and shows that evidence. No trust score is computed, and credential nodes are key names only.
• Authority Epochs - retained local snapshots with comparison between any two: added/removed authority, permission expansion or reduction, new MCP references, new API origins, new credential-key exposure, new external destinations, and new production/destructive capability.
• Dangerous action chains - deterministic risk indicators such as credential access -> external send, credential access -> destructive capability, filesystem access -> network send, and package mutation -> deployment. Each shows its nodes, edges, reason, source evidence and a remediation suggestion. These are indicators, never a declaration that an agent is unsafe or malicious.
• Reciprocal Agent <-> MCP view - deterministic name matches between an agent's declared MCP servers and this workspace's MCP inventory, with truthful coverage. "ENFORCED VIA LOCAL TRUST GATE" is shown by ECZ-ID MCP Trust when it holds a live gate session; Resolver public proof stays separate.
• Remediation - reviewable config patches: preview, diff, timestamped backup, atomic apply, rollback.

Developer Trust Pro unlocks both Agent Trust Pro and MCP Trust Pro. Community keeps working if a Pro entitlement is absent or expires - only Pro features deactivate, and your locally retained history stays.

Useful for

Useful across many legitimate roles. Commonly used by:

• AI-agent and MCP tool builders
• Platform and AppSec teams integrating agents
• Enterprise architects reviewing agent posture
• Reviewers and architects evaluating third-party agents

Relevant when you are wiring an agent or MCP tool, before granting an agent tool access, an evaluator asks for agent provenance, you are reviewing a third-party agent.

What you can do in under a minute

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

What it looks for

• Agent manifests (agent.yaml, agent.json) and tool / action specs.
• Agent frameworks (LangChain/LangGraph, CrewAI, AutoGen, Semantic Kernel, LlamaIndex, OpenAI, Anthropic).
• MCP tool configuration and webhooks an agent may call.
• Whether an ecz-agent.json / .well-known/ecz-agent.json resolver reference is present.

Example result

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

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?

A scan you run reads filenames and paths, then locally inspects the contents of files it classified as agent or MCP JSON configuration (strict JSON only, 256 KiB limit) to build the Agent X-Ray. Only names, enums, counts and fingerprints are kept - environment variable values are never read into results, and nothing is uploaded. YAML and other formats are observed by filename only and labelled as such.

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 agent frameworks can it detect?

Common agent manifests and frameworks - LangChain/LangGraph, CrewAI, AutoGen, Semantic Kernel, LlamaIndex - plus tool/action specs and MCP tool configurations.

What does the manifest scaffold command change?

Only ecz-agent.json, and only when you invoke it. It reads and writes that single local file; nothing else is touched.

Does it run or call my agents?

No. It inspects local files only. It never executes an agent, tool or webhook.

Is the Authority Graph inferred or invented (Pro)?

Neither - every node and edge comes from deterministic discovered evidence and carries its source. An agent->MCP edge is drawn only when the agent's declared server name also appears in this workspace's MCP inventory. No trust score is computed.

Are dangerous action chains saying my agent is unsafe (Pro)?

No. They are risk indicators derived from declared configuration, each with its nodes, edges, reason and evidence, so you can judge for yourself. They never declare an agent unsafe or malicious.

When does the reciprocal view show ENFORCED (Pro)?

Agent Trust never mediates MCP traffic, so it shows coverage as OBSERVED. "ENFORCED VIA LOCAL TRUST GATE" for an MCP target is shown by ECZ-ID MCP Trust while it holds a live gate session for that exact server. Resolver public proof is a separate concept.

What happens to Pro features when my entitlement expires?

Pro features deactivate on the next verification; Community continues in full and your locally retained history is kept. Entitlements are verified locally with asymmetric (ES256) cryptography; the entitlement token is never displayed or transmitted by this extension.

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. Does not imply that any agent is acceptable or unacceptable. The optional scaffold/validate command reads only ecz-agent.json, and only when you invoke it.
• 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 Agent Trust (publisher EcoCitizenz) and install it.
2. Open a project and trust the workspace.
3. Run ECZ-ID Agent Trust: Scan Workspace and review the grouped findings.

Free vs Pro vs supported setup

• Community (free, local-first): detected agent surfaces with neutral posture, Agent X-Ray, missing-public-proof findings, and Resolver / supported-setup routes - no sign-in and no purchase to run a check.
• Agent Trust Pro (paid, still local): Authority Graph with evidence on every edge, Authority Epochs, dangerous action-chain indicators, the reciprocal Agent <-> MCP view, and reviewable remediation. Activate with a Developer Trust entitlement; the Developer Trust Pro bundle unlocks MCP Trust Pro too.
• Supported setup (TrustOps): maintained ECZ-ID identity, public proof and lifecycle for agent 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; Pro and supported setup are separate, optional steps.

Python / CLI

Prefer Python, CI or terminal automation?

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

• Open the matching Python package: https://pypi.org/project/ecz-id-agents/
• 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