Trust by design

Security must be enforced, not promised.

ZUQMCP is in development. These are design requirements and release gates—not completed security certifications.

Every request must prove which user and website it belongs to, including MCP tool calls and background tasks.

Cloud access will require site-administrator authorization with a working revoke path.

Risky writes must be bound to an approved operation and its exact arguments; not just a friendly confirmation in the chat.

HTTPS, scoped tokens, rotation, encrypted storage, secret management, least privilege and audit logs are planned requirements.

Restore verification is required before shipping sensitive maintenance and bulk operations.

Threat modeling, automated tests and security assessment must be completed before public SaaS access.