Setup guidance · High-risk MCP servers
ECZ-ID MCP Assurance Plus™
Stronger provider-side resolver posture for MCP servers with high-risk tools. £499/mo. SKU ECZ-BUNDLE-MCP-ASSURANCE-PLUS. Setup happens in TrustOps. Developer Gateway documents and routes.
When MCP Assurance Plus fits
- Your MCP server exposes high-risk tools that mutate state, move money, or release sensitive data.
- Relying parties need a stronger resolver-identifiable posture before they enable those tools.
- You want documented dangerous_tool_flags and a tool_inventory_hash referenced from your manifest.
What setup covers
- Everything in MCP Assurance.
- Tool inventory hash and dangerous_tool_flags references in the manifest.
- API Passport dependency declarations for every high-risk tool.
- Operator guidance for fail-closed verification on the relying-party side.
Canonical product reference
- Name: ECZ-ID MCP Assurance Plus™
- Price: £499/mo
- SKU: ECZ-BUNDLE-MCP-ASSURANCE-PLUS
- Role: stronger provider-side resolver posture for high-risk tools.
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.