Inspects MCP server manifests for ECZ-ID configuration and public evidence posture.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ecz-id-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ECZ-ID MCP Server Inspection `ecz-id-mcp` statically inspects MCP server manifests for **ECZ-ID configuration posture**, transport posture and identity. Part of the ECZ-ID PyPI family. It **inspects, explains and routes only**. It **never starts an MCP server**, never executes a configured command, never connects to a transport, and never creates another MCP identity or Official MCP Registry entry. It never issues or activates an ECZ-ID, never prices or carts, and never certifies. It is **not** a safety/compliance/insurance/premium decision and **not** a security, capability or behavioural proof. Missing public proof is neutral. **Local policy decides. Re-check before reliance.** ## One-command first run ```console $ ecz-id-mcp inspect ./my-mcp-server ECZ-ID inspection: ./my-mcp-server [ecz-id-mcp] A. configuration posture : PRESENT B. public proof posture : NOT_CHECKED (neutral) ... local policy decides; re-check before reliance ``` ## Supported inputs * A directory or manifest file (static JSON only). Recognised surfaces, each labelled with the configuration **dialect** it came from: `.vscode/mcp.json`, `.mcp.json`, `.cursor/mcp.json`, `.claude/mcp.json`, Copilot / user-level MCP config, `claude_desktop_config.json`, `ecz-mcp.json` (and `.well-known/`), `mcp_server_manifest.json`, `mcp.json` / `.mcp/*.json`, and the Official MCP Registry `server.json` publication manifest. * Observes server name, declared tools (and read-only markers), declared stdio / remote transport posture, invocation command and args (**never executed**), remote endpoints (**never connected**, credentials and query string omitted), and registry / package / repository identity. * Observes pinned-vs-floating invocation (version pin present or not) and compares declared package identity with a co-located `pyproject.toml`. ## Protocol generation awareness Converged onto `ECZ-BASELINE-2026-08-13`. `MCP 2026-07-28` is the current generation; earlier generations stay…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.