How MCXAI decides a tool is ready
A passing build is only the start. MCXAI evaluates whether a working product accepts valid input, rejects unsafe input, produces reviewable output and explains where it can fail. Interface previews are assessed against a separate, narrower promise.
Product checks
Valid, invalid, empty, oversized and provider-failure cases are exercised. Retry behavior, privacy controls and exports are reviewed before a tool is labelled working.
Page checks
Metadata, canonical, server-rendered content, internal links, structured data, mobile behavior and keyboard paths are verified for every public page.
Decision rule
A provider-dependent route may be public only as a distinct, reviewed interface preview that never claims to process input or return a provider result. Otherwise it remains noindex and absent from navigation and sitemaps until the workflow and evidence pass.