Setup guidance · Provider-side resolver posture
ECZ-ID MCP Assurance™
Provider-side resolver posture setup guidance for MCP servers, tools, and providers. £199/mo. SKU ECZ-BUNDLE-MCP-ASSURANCE. Setup happens in TrustOps. Developer Gateway documents and routes.
When MCP Assurance fits
- You operate an MCP server, tool, or provider surface.
- You want resolver-identifiable posture for your MCP binding so relying parties can verify before they call.
- You are ready to publish a /.well-known/ecz-mcp.json manifest with non-secret references.
What setup covers
- Parent ECZ-ID binding via TrustOps (if not already in place).
- MCP server binding with a canonical manifest_hash and non-secret package_ref / repo_ref / container_ref.
- API Passport dependency declarations where the MCP tools call APIs.
- Guidance for relying parties on how to interpret your Resolver state.
Canonical product reference
- Name: ECZ-ID MCP Assurance™
- Price: £199/mo
- SKU: ECZ-BUNDLE-MCP-ASSURANCE
- Role: provider-side resolver posture setup guidance.
No overclaim posture
- No public resolver proof found yet does not mean unsafe.
- Re-check before reliance.
- Local policy decides.
- The verifier does not create or change verification state.
ECZ-ID separates setup, verification state, and public proof so operators can prepare evidence and relying parties can re-check before they act. TrustOps handles setup. Resolver remains the public proof surface. The verifier does not create or change verification state. Start setup in TrustOps when you operate the target. Share resolver guidance when you do not. Local policy decides. Re-check before reliance.