Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Track shared Clize runtime evolution and changes to domain, inbox, hosting and merchant profiles without counting profiles as implementations.
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
One agent-facing runtime for domain, inbox, sites and storefront services.
What we know
Clize provides an agent-native service stack covering domain registration, email inbox, website publishing and storefront workflows. @clize/clize is the consolidated runtime; Clize Domains, Inbox, Sites and Storefront are service areas, not four independent installed servers. Purchase, send and refund paths require transaction/approval controls.
Maintenance / activity evidence
- The owner-reviewed canonical Clize runtime @clize/clize, registry identity ai.clize/clize, exposes four current product profiles around one MCP runtime.
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Potential authority to send email, publish web content, manage domains and purchases according to configured Clize permissions. Reported action classes: Send email and manage mailbox state (where enabled); Publish or update public sites/storefronts; Request domain purchases after user confirmation; Request commerce/refund actions according to service confirmation gates. Complete write authority is not verified.
- Authentication not yet verified.
- Sensitive access: Email contents and recipients, Domain account details, Storefront/customer and payment data
- Email, purchasing and public publishing are externally consequential.
- Confirmation is not proof of blanket permission; specific per-action gates apply.
Full authority, access and evidence limits are available in Review context and Access & risk.
All limitations / Review context
Have runtime capabilities or profile-specific operational boundaries changed across domains, inbox, sites and storefront?
The explicit owner-reviewed correction approves accurately scoped public tracking of Clize; this is neither installation safety nor security certification.
- Email, purchasing and public publishing are externally consequential.
- Confirmation is not proof of blanket permission; specific per-action gates apply.
- Potential authority to send email, publish web content, manage domains and purchases according to configured Clize permissions.
- Emails, domains, sites and storefront data are handled by Clize and potentially external registrars or payment providers.
- Reviewed write actions: Send email and manage mailbox state (where enabled); Publish or update public sites/storefronts; Request domain purchases after user confirmation; Request commerce/refund actions according to service confirmation gates
- Sensitive access: Email contents and recipients, Domain account details, Storefront/customer and payment data
- Complete write authority is not verified.
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- Runtime, dependency vulnerabilities, installation readiness and complete tool permissions were not independently audited in Phase E.
- Domains, inbox, sites and storefront are profiles of one shared runtime; profile-specific operational authority must be assessed before use.
- No higher-tier recommendation, production-readiness claim, installation certification or complete client/tool audit is supplied.
- verified current CLI entrypoint and MCP transport
- runtime authentication/env variable names
- complete tool inventory and data retention
- The npm shared runtime is distinct from individual @clize/domains, @clize/inbox, @clize/sites and @clize/storefront source entries.
- Actual wallet/payment authorization and transactional confirmation vary by operation.
- Exact version-specific command/transport and credential environment variables should not be inferred without package documentation.
- Publishing, email and domain purchase can have external consequences.
- Do not materialize source-only @clize/* subordinate package identities as separate Radar MCPs.
Original activity observations
- The owner-reviewed canonical Clize runtime @clize/clize, registry identity ai.clize/clize, exposes four current product profiles around one MCP runtime.
Technical identity
npm/@clize/clize- Exact implementation source
- https://www.npmjs.com/package/@clize/clize ↗
- Reviewed resource type
- Gateway
- Package identity
- npm:@clize/clize
- Profiles of one shared MCP runtime
- Domains ·
npm/@clize/domains - Inbox ·
npm/@clize/inbox - Sites ·
npm/@clize/sites - Storefront ·
npm/@clize/storefront
- Domains ·
- MCP registry identity
- ai.clize/clize
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- Package registry ↗
@clize/clize
Recorded package identity, distribution or download evidence.
- Package registry metadata ↗
@clize/domains
Recorded package identity, distribution or download evidence.
Includes shared evidence.
- Package registry metadata ↗
@clize/inbox
Recorded package identity, distribution or download evidence.
Includes shared evidence.
- Package registry metadata ↗
@clize/sites
Recorded package identity, distribution or download evidence.
Includes shared evidence.
- Package registry metadata ↗
@clize/storefront
Recorded package identity, distribution or download evidence.
Includes shared evidence.
- Evidence source ↗
clize.ai/
Source material retained for this review.
Includes references whose attribution is not established.
- Evidence source ↗
clize.ai/docs/commands/
Source material retained for this review.
Includes references whose attribution is not established.
Setup · Watchlist
Gateway setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsOptional host-registration example only; follow the CLI workflow unless this integration was separately configured: Install Clize CLI, run `clize login`, then register `claude mcp add clize -- clize-mcp` or `codex mcp add clize -- clize-mcp`.
publisher install or stdio launch · Publisher instructions
npm i -g @clize/clizeConfigure / authenticate
MCP100 setup guideClize CLI: follow published installer and `clize login`, then `clize check`. This is a developer platform CLI with optional integrations, not necessarily a standalone stdio MCP server.
Check connection
Suggested checkPublisher `clize check` verifies login; avoid paid domain purchases and deployments.
Remove / uninstall / revoke
MCP100 setup guideDisconnect Clize integrations in the Clize account/CLI; uninstall the Clize CLI using the same original installer. Do not assume a direct MCP host registration exists.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Official Documentation & Sources
What it does
Clize provides an agent-native service stack covering domain registration, email inbox, website publishing and storefront workflows. @clize/clize is the consolidated runtime; Clize Domains, Inbox, Sites and Storefront are service areas, not four independent installed servers. Purchase, send and refund paths require transaction/approval controls.
- Capability
- Productivity & Collaboration
- Resource type
- Gateway
- Best fit
- One agent-facing runtime for domain, inbox, sites and storefront services.
Representative uses
- Search/register domains subject to purchase confirmation
- Set up and manage agent-facing email and send messages where permitted
- Create/publish sites and storefront content
- Review paid service or commerce operations before confirmation
Limitations
- The npm shared runtime is distinct from individual @clize/domains, @clize/inbox, @clize/sites and @clize/storefront source entries.
- Actual wallet/payment authorization and transactional confirmation vary by operation.
- Exact version-specific command/transport and credential environment variables should not be inferred without package documentation.
- Publishing, email and domain purchase can have external consequences.
- Do not materialize source-only @clize/* subordinate package identities as separate Radar MCPs.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Not documented in the reviewed sources
- Permissions
- Potential authority to send email, publish web content, manage domains and purchases according to configured Clize permissions.
- Data handling
- Emails, domains, sites and storefront data are handled by Clize and potentially external registrars or payment providers.
- Cost
- service_plan
- Risk and cautions
- Email, purchasing and public publishing are externally consequential.
Access scope and cautions
- Write actions
- Not verified Send email and manage mailbox state (where enabled) Publish or update public sites/storefronts Request domain purchases after user confirmation Request commerce/refund actions according to service confirmation gates
- Sensitive access
- Email contents and recipients Domain account details Storefront/customer and payment data
- Risk level
- high
- Security notes
- Confirmation is not proof of blanket permission; specific per-action gates apply.
The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.
FAQ
Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.