Pointing your own domain at a Sakupa site: what "published" actually requires

A note up front: I am not Sakupa's developer. I found this MCP server while looking into how AI agents publish small websites, and this is my own reading of its official manual. This is not a hands-on usage report. Sakupa publishes static sites from an AI chat, without user accounts. That design makes one question interesting: when you point your own domain at the site, what counts as "published"? The bind step, in three parts Ask for the connection. The bind tool handles the custom-domain connection. Confirm it through DNS. The domain's settings are checked through DNS. If that check does not pass, the process does not move forward. "Published" is only announced after a live check. The connection is not called published just because the domain was attached. Only when the state is active and the site returns HTTP 200 is it announced as published. That third step is the point of this design. Attaching a domain and publishing a site are treated as two different things, and the gap between them is closed by a check, not by an assumption. What happens when the check fails If the DNS settings are wrong, or have not propagated yet, the check does not pass, and no published announcement is made. In practice that means "I thought I connected it" cannot run ahead of "it actually opens." For a small business site, that ordering matters: a domain that looks connected but does not open is worse than a domain that is honestly still pending. The surrounding design, briefly The same caution shows up elsewhere in the tool list: analyze is a read-only pre-publish check that warns about unsuitable files before anything goes live. Publishing, deletion, and credential rotation all pass through a preview and a confirmation step. Deleting a free site is explicitly irreversible. Payments never go through the agent itself. subscribe creates a Stripe signup link, and the person pays on Stripe's page. There is no account registration, so credentials live locally. If you change machines, recover offers a device path or a DNS path, and whether old credentials are invalidated is always the person's choice, not the agent's. Limits worth knowing Sakupa is for static sites only. It does not cover web apps with databases or login features. It is also a relatively new service (first published on npm in July 2026, per the official timeline). The usual free preview is 30 days, with paid plans from 200 yen per month, contracted per site. The domain lesson generalizes: in a workflow where an agent does the work, "done" should mean "checked live," not "requested." Sakupa's bind step builds that distinction into the procedure itself. Links Official site: https://sakupa.com/ Product page: https://sakupa.com/product/ Manual: https://sakupa.com/manual/ npm: @sakupa/mcp