ChatGPT Sites 上 HN 热议：可托管 MCP 服务器
Sites 冲上 HN 首页后，讨论焦点从「能不能用」转向原型与生产的边界，以及 OpenAI 确认 Sites 可托管 MCP 服务器带来的授权问题。
On Oct 3, ChatGPT Sites front-paged Hacker News: 209 points, 218 comments. Sites had been in public beta for months. HN forced the question product pages skip. Is this a toy, a prototype host, or something real? Builders spent less time on whether it works and more on what it kills: prototypes vs production hosting on .chatgpt.site, durability and lock-in vs custom domains, how it compares to Claude Artifacts. The thread's five-word verdict: "wow, there goes Lovable's moat." The calmer consensus was more interesting. The sweet spot is hour-scale prototypes that are playable the same day: a maze game after a concert, a festival schedule, a campus food guide. The real fork is prototype vs production. Deployed means live, there is no separate staging URL, and the docs say it plainly: not for PHI, payments, or residency-sensitive data. Then the twist. OpenAI confirmed on Oct 1 that Sites can host MCP servers. The hosting tax on callable tools just died. When deploying the tool costs nothing, gating what the tool is allowed to do becomes the whole problem. The thread argued about lock-in to .chatgpt.site. The sharper question is who authorizes what those hosted tools can touch.