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.
Available components
Last scanned (23 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 790 tokens (~112/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Sept 26 0
- Schema quality: 97 → 112 ▼ functional
- “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” cosmetic
- 27 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://trust-mcp.ecocitizenz.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trust-mcp.ecocitizenz.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 19 Aug 2026 | 19 Feb 2027 | RSA 2048 | SHA256-RSA | 57027044b7d6df1a0648f850428fa15 |
| SANs: trust-mcp.ecocitizenz.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trust-mcp.ecocitizenz.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ecocitizenz.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trust-mcp.ecocitizenz.com/mcp | Verified | 200 | |
| http (plaintext) | http://trust-mcp.ecocitizenz.com/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_request_to_resolve Create a neutral Request-to-Resolve (authenticated) ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consent_mode | string | yes | – |
| idempotency_key | string | – | – |
| requested_evidence_category | string | yes | – |
| resolver_ref | string | – | – |
| target_descriptor | string | yes | – |
| target_type | string | yes | – |
No output schema declared.
No examples provided.
explain_status Explain ECZ-ID status ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecz_id | string | yes | ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123 |
No output schema declared.
No examples provided.
find_product Find the next best ECZ-ID action ~130
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_current_state Get current ECZ-ID state ~90
Return the narrow current Resolver-derived state for an ECZ-ID (state, checked_at, Resolver link). No risk/safety/compliance inference.
| Name | Type | Req | Description |
|---|---|---|---|
| ecz_id | string | yes | ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123 |
No output schema declared.
No examples provided.
get_install_instructions Get official install routes ~75
Return deterministic official install/discovery routes for an ECZ-ID product or surface (canonical URLs only; planned Microsoft surfaces carry no URLs).
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product slug: mcp-trust | agent-trust | developer-trust | resolver | developer-gateway | trustops | mcp-services | msp |
No output schema declared.
No examples provided.
get_resolver_link Get Resolver proof link ~81
Return the deterministic public Resolver proof/re-check URL for an ECZ-ID. No network call.
| Name | Type | Req | Description |
|---|---|---|---|
| ecz_id | string | yes | ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123 |
No output schema declared.
No examples provided.
resolve_identity Resolve an ECZ-ID ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecz_id | string | yes | ECZ-ID identifier. Parent, e.g. ECZ-GB-RBS1NW; or child Passport, e.g. ECZ-GB-RBS1NW::MCP_PASSPORT-ABC123 |
No output schema declared.
No examples provided.
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.
remote · trust-mcp.ecocitizenz.com
claude mcp add --transport http com-ecocitizenz-trust-mcp 'https://trust-mcp.ecocitizenz.com/mcp'
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 71 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.