# ECZ-ID Trust MCP (remote · trust-mcp.ecocitizenz.com)

Read-only ECZ-ID Business Passport state lookup via the public ECZ-ID Resolver. Reports state only.

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `trust-mcp.ecocitizenz.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-ecocitizenz-trust-mcp/trust-mcp.md), [page](https://verifymcp.io/servers/com-ecocitizenz-trust-mcp/trust-mcp)

## Channel facts

- Endpoint: `https://trust-mcp.ecocitizenz.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 790 tokens (~112/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ECZ-ID Trust MCP server?

ECZ-ID Trust MCP is a hosted endpoint at https://trust-mcp.ecocitizenz.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-ecocitizenz-trust-mcp 'https://trust-mcp.ecocitizenz.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ecocitizenz-trust-mcp": {
      "url": "https://trust-mcp.ecocitizenz.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ecocitizenz-trust-mcp": {
      "type": "http",
      "url": "https://trust-mcp.ecocitizenz.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ecocitizenz-trust-mcp]
url = "https://trust-mcp.ecocitizenz.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ecocitizenz-trust-mcp": {
      "type": "remote",
      "url": "https://trust-mcp.ecocitizenz.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ecocitizenz-trust-mcp --url 'https://trust-mcp.ecocitizenz.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ecocitizenz-trust-mcp:
    url: "https://trust-mcp.ecocitizenz.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ecocitizenz-trust-mcp": {
      "Transport": "http",
      "Url": "https://trust-mcp.ecocitizenz.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ecocitizenz-trust-mcp -t streamable-http -u 'https://trust-mcp.ecocitizenz.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ecocitizenz-trust-mcp": {
      "type": "http",
      "url": "https://trust-mcp.ecocitizenz.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 65, +1)

- [functional regression] Schema quality: 97 → 112
- [cosmetic] “explain_status” reworded the description of “ecz_id”
- [cosmetic] “get_current_state” reworded the description of “ecz_id”
- [cosmetic] “get_resolver_link” reworded the description of “ecz_id”
- [cosmetic] “resolve_identity” reworded the description of “ecz_id”

### 2026-09-09 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `resolve_identity` (~104 tokens)

Resolve an ECZ-ID

Resolve an ECZ-ID through the public ECZ-ID Resolver and return the exact canonical state with checked_at, Resolver proof link, re-check action and the local-policy caveat. Never asserts safety, approval or compliance.

Input parameters:

- `ecz_id` (string, required): ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123

### `get_current_state` (~90 tokens)

Get current ECZ-ID state

Return the narrow current Resolver-derived state for an ECZ-ID (state, checked_at, Resolver link). No risk/safety/compliance inference.

Input parameters:

- `ecz_id` (string, required): ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123

### `get_resolver_link` (~81 tokens)

Get Resolver proof link

Return the deterministic public Resolver proof/re-check URL for an ECZ-ID. No network call.

Input parameters:

- `ecz_id` (string, required): ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123

### `explain_status` (~108 tokens)

Explain ECZ-ID status

Deterministically render the exact ECZ-ID status using the claims-safe renderer (VERIFIED is an ECZ-ID state, not a Microsoft certification). Absence of evidence renders the approved neutral wording — never "unsafe". No LLM.

Input parameters:

- `ecz_id` (string, required): ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123

### `find_product` (~130 tokens)

Find the next best ECZ-ID action

Given narrow context flags, return ONE best next ECZ-ID product action (free/community routes win where correct; neutral context routes to free public verification).

Input parameters:

- `agent_concern` (boolean)
- `business_identity_missing` (boolean)
- `deeper_evidence_required` (boolean)
- `developer_local_workflow` (boolean)
- `implementation_assessment_needed` (boolean)
- `mcp_concern` (boolean)
- `multi_tenant_estate` (boolean)
- `org_wide_governance` (boolean)
- `software_supply_chain_evidence` (boolean)

### `get_install_instructions` (~75 tokens)

Get official install routes

Return deterministic official install/discovery routes for an ECZ-ID product or surface (canonical URLs only; planned Microsoft surfaces carry no URLs).

Input parameters:

- `product` (string, required): Product slug: mcp-trust | agent-trust | developer-trust | resolver | developer-gateway | trustops | mcp-services | msp

### `create_request_to_resolve` (~124 tokens)

Create a neutral Request-to-Resolve (authenticated)

AUTHENTICATED: create a neutral, shareable request for independently re-checkable ECZ-ID evidence. Requires a Microsoft Entra bearer token with the RequestToResolve.Create scope (or app role). It never verifies a target, never sends messages, and absence of evidence is never rendered as unsafe.

Input parameters:

- `consent_mode` (string, required)
- `idempotency_key` (string)
- `requested_evidence_category` (string, required)
- `resolver_ref` (string)
- `target_descriptor` (string, required)
- `target_type` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ecocitizenz-trust-mcp/trust-mcp#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59
- 2026-08-29: 59
- 2026-08-28: 58
- 2026-08-27: 58
- 2026-08-26: 57

## Common questions

### What is the ECZ-ID Trust MCP server?

ECZ-ID Trust MCP is listed in the public MCP registry as com.ecocitizenz/trust-mcp. Read-only ECZ-ID Business Passport state lookup via the public ECZ-ID Resolver. Reports state only. This page covers its hosted endpoint (https://trust-mcp.ecocitizenz.com/mcp).

### Is the ECZ-ID Trust MCP server safe to use?

ECZ-ID Trust MCP scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ECZ-ID Trust MCP server expose?

ECZ-ID Trust MCP exposes 7 tools: resolve_identity, get_current_state, get_resolver_link, explain_status, find_product, and 2 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.

### Does the ECZ-ID Trust MCP server require authentication?

No. We connected to ECZ-ID Trust MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ECZ-ID Trust MCP server still maintained?

ECZ-ID Trust MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://trust-mcp.ecocitizenz.com/mcp
- Website: https://developers.ecocitizenz.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-ecocitizenz-trust-mcp/trust-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ecocitizenz-trust-mcp/trust-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-ecocitizenz-trust-mcp/trust-mcp