Ask who operates an MCP server. Get an answer you can re-check.

curl -sS -X POST https://trust-mcp.ecocitizenz.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/list' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{"_meta":{
        "io.modelcontextprotocol/protocolVersion":"2026-07-28",
        "io.modelcontextprotocol/clientCapabilities":{}}}}'

Contract: ECZ-ID Trust MCP Contract v1.0.0, frozen 19 August 2026, provider-neutral. The Trust MCP Server accepts protocol 2026-07-28 and negotiates the session version with the client; a client that offers 2025-11-25 is served on 2025-11-25.

# Human
https://resolver.ecocitizenz.org/p/ECZ-GB-RBS1NW

# Machine
curl -sS https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json | jq '.resolver_v2'

Identifier format, from the live server's own input schema: ^ECZ(-[A-Z0-9]{2,32}){1,4}$, maximum 64 characters. Example: ECZ-GB-RBS1NW.

Five concepts, five field paths. Integrate against resolver_v2; the blocks outside it are legacy compatibility.

"machine_policy": {
  "recommended_machine_action": "ALLOW_PARENT_IDENTITY_VISIBILITY_ONLY",
  "high_risk_action": "FAIL_CLOSED_UNLESS_LIVE_BINDING_AND_EVIDENCE_AVAILABLE",
  "fail_closed_states": ["REVOKED","SUSPENDED","DEGRADED","MISMATCH","PROOF_UNAVAILABLE",
                         "PUBLIC_PROJECTION_UNAVAILABLE","ACTIVE_ABUSE_FLAGGED","UNKNOWN"],
  "machines_should_use": ["state.lifecycle_state","state.reliance_level","binding.state",
                          "evidence.public_receipt_state","ledger.public_receipt_state",
                          "agent_trust.status"]
}

STATE=$(curl -sS https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json \
        | jq -r '.resolver_v2.state.lifecycle_state // "UNKNOWN"')
case "$STATE" in
  REVOKED|SUSPENDED|DEGRADED|MISMATCH|PROOF_UNAVAILABLE|PUBLIC_PROJECTION_UNAVAILABLE|ACTIVE_ABUSE_FLAGGED|UNKNOWN)
    echo "fail closed: $STATE"; exit 1 ;;
  *) echo "proceed under local policy: $STATE" ;;
esac

npx -y @ecocitizenz/ecz-id-mcp-verifier --target "ECZ-GB-RBS1NW" --policy PREFER

{
  "target": "ECZ-GB-RBS1NW",
  "target_type": "ecz_id",
  "policy_mode": "PREFER",
  "result_state": "RESOLVER_VERIFIABLE",
  "reason_codes": [],
  "resolver_url": "https://resolver.ecocitizenz.org/p/ECZ-GB-RBS1NW",
  "machine_json_url": "https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json",
  "primary_action": "VIEW_RESOLVER_PROOF",
  "verifier_writes_truth": false,
  "verifier_activates_proof": false,
  "verifier_marks_bound": false,
  "local_policy_decides": true,
  "recheck_before_reliance": true,
  "no_safety_or_approval_inference": true,
  "no_source_uploaded": true,
  "no_secrets_uploaded": true,
  "no_telemetry": true,
  "exit_code": 0
}

Add --report for a human-readable version, --sarif <path> for SARIF output, --offline to run with no network at all, and --capabilities to print the tool's own machine-readable capability profile. When this page and --capabilities disagree, --capabilities is right.

Three local policy modes, and they only ever govern your own gate:

OPEN

Missing public proof is informational. Exit 0.

PREFER

Missing public proof warns on stderr. Exit 0. This is the Action's default; the CLI defaults to OPEN.

REQUIRE

Missing public proof fails closed — exit 1, or exit 5 if the network was attempted and failed. Your CI gate. Not a global verdict about anyone.

A mismatch, revocation, suspension or expiry exits non-zero under every mode, because those are deterministic findings about published state rather than questions about your appetite for risk.

The same package is a local MCP server. It prints its own host config — do not transcribe it by hand.

npx -y @ecocitizenz/ecz-id-mcp-verifier --print-mcp-config

{
  "mcpServers": {
    "ecz-id": {
      "command": "npx",
      "args": ["-y", "-p", "@ecocitizenz/ecz-id-mcp-verifier", "ecz-id-mcp-server"]
    }
  }
}

ecz_check_target

the full canonical result, plus the computed exit code

ecz_recheck_resolver

a read-only Resolver re-check, forced to OPEN so it stays informational

ecz_explain_result

a public-safe explanation of states and codes that already exist — it never invents one

The -p flag is load-bearing: it selects the package, then runs the ecz-id-mcp-server binary from it. Without -p, npx looks for a package named ecz-id-mcp-server, which does not exist.

Free to use — personal, organisational, development, CI/CD and internal business use, at no charge, under the ECZ-ID Proprietary Limited-Use License. That licence is not an open-source licence and we do not describe it as one.

name: ECZ-ID posture

on:
  pull_request:
  push:
    branches: [main]

# The Action only reads and reports.
permissions:
  contents: read

jobs:
  ecz-id:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Check ECZ-ID Resolver posture
        id: ecz
        uses: <ecz-id-mcp-verifier action ref — take the exact tag from the repository's own README>
        with:
          target: "https://api.example.com/.well-known/ecz-mcp.json"
          target-type: "mcp_server"
          policy: "PREFER"
          operator: "third_party"
          timeout-ms: "5000"

      - name: Route on state
        run: |
          case "${{ steps.ecz.outputs.result-state }}" in
            RESOLVER_VERIFIABLE)
              echo "Public proof found. Local policy decides sufficiency." ;;
            NO_PUBLIC_RESOLVER_PROOF_FOUND|PARTIAL_PUBLIC_PROOF_FOUND|SETUP_REQUIRED)
              echo "No published proof yet. Not a failure signal." ;;
            MISMATCH|REVOKED|SUSPENDED|EXPIRED|DEGRADED)
              echo "Deterministic finding. Failing this job."; exit 1 ;;
            *)
              echo "Informational: ${{ steps.ecz.outputs.result-state }}" ;;
          esac

To make it a hard gate instead, change one input: policy: REQUIRE. That is your decision about your repository, not a verdict this layer issues about anyone else's.

Nine inputs, nine outputs. operator is never auto-inferred — the routing advice differs depending on whether the target is yours, and a wrong guess sends you to the wrong place.

Inputs

Outputs

Air-gapped runners: set no-network: "true" (or its alias offline: "true"). Offline runs perform deterministic classification only — no lookup, no network. In every mode the Action uploads no source, no secrets and no telemetry.

These are software products. They are not the four fixed-scope professional engagements published on this site, which are a different thing bought a different way.

TrustOps issues entitlement and holds order state. This page only routes: it does not sell, does not know what you already hold, and does not create or amend any ECZ-ID state. Tiers and prices as published on 23 August 2026 — the product page is authoritative.

Verified 23 August 2026. The Trust MCP Server implements Trust MCP contract v1.0.0, frozen. Version numbers for the npm package, the GitHub Action and the VS Code extensions are not published here: the npm release line and the repository's tag line are not at the same release, so a number on this page would be right for some readers and wrong for others. Run the command shown above to print the version you actually have, or open the package page for the current published version.

Three of the ten Python distributions matter for MCP work: ecz-id (the shared core), ecz-id-mcp (inspects MCP manifests — server.json, mcp_server_manifest.json, mcp.json, .mcp.json) and ecz-id-agents (inspects agent projects). They are static inspectors: they never start a server, never execute a configured command and never connect to a transport. inspect makes no network call unless you pass --check-public; recheck opts in by default.

The ECZ-ID MCP Verifier also publishes an MCP Registry identity: io.github.Ecocitizenz/ecz-id-mcp-verifier, declared in its server.json against the 2025-12-11 server schema, npm transport stdio.

One behaviour worth knowing before you point an agent at any of this: external content — target strings, Resolver responses, error text — is treated as data, never as instructions. That rule is written into the ECZ-ID MCP Verifier's MCP tool module, and the deterministic status renderer on the Trust MCP Server uses no LLM at all.

Developer Gateway — developers.ecocitizenz.com

Guides, integration patterns, and the canonical schemas. The Gateway owns every schema in the estate; this page owns none of them.ECZ-ID Developer Gateway↗

ECZ-ID Resolver — resolver.ecocitizenz.org

Public proof. Look up any ECZ-ID, read the record, re-check it whenever you need to.ECZ-ID Resolver↗

TrustOps — trustops.ecocitizenz.com/start

Setup, entitlement and lifecycle. If you operate a surface and want it identifiable, this is where that begins. Public proof appears after backend activation, not at checkout.TrustOps↗

If you would rather have this assessed than integrate it yourself, four fixed-scope MCP engagements are published with full prices and scope at /services. Nothing on this page requires any of them.

The four fixed-scope MCP engagements, with published prices and scope→