Security & Testing

ecocitizenz.com

Resolves and verifies ECZ-ID identities through the public resolver, explaining status and recommending next actions.

1 endpoint7 known toolsFirst detected July 25, 2026Last detected July 29, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: eczid-trust-mcp
Version: 0.2.0

Capabilities

tools.listChanged

Server instructions

ECZ-ID Trust: resolve ECZ-ID identifiers and evidence state via the public Resolver, explain exact canonical state, route to the single best next ECZ-ID product action, and (authenticated) create neutral Request-to-Resolve records. Results render ECZ-ID state exactly and never assert safety, approval, compliance or Microsoft certification. Local policy decides whether a signal is sufficient.

Known tools 7

resolve_identity

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.

Inferred read-only

get_current_state

Return the narrow current Resolver-derived state for an ECZ-ID (state, checked_at, Resolver link).

Inferred read-only

get_resolver_link

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

Inferred read-only

explain_status

Deterministically render the exact ECZ-ID status using the claims-safe renderer (VERIFIED is an ECZ-ID state, not a Microsoft certification).

Inferred read-only

find_product

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).

Inferred read-only

get_install_instructions

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

Inferred read-only

create_request_to_resolve

AUTHENTICATED: create a neutral, shareable request for independently re-checkable ECZ-ID evidence.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.eczid-trust-mcp]
url = "https://trust-mcp.ecocitizenz.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: eczid-trust-mcp
Remote MCP URL: https://trust-mcp.ecocitizenz.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "eczid-trust-mcp",
  "transport": "streamable-http",
  "url": "https://trust-mcp.ecocitizenz.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.