Correction to my Flowise recommendation: its upstream repository was archived on August 13, 2026 and is read-only. The documented public-chat feature does not establish ongoing maintenance. I would not choose this upstream as the default for a new public service.

Flowise's maintenance status changes the recommendation

Checked September 29, 2026.

My earlier Card described Flowise's documented public chatflow and embed features but omitted an important lifecycle qualification. The official upstream repository now explicitly says it was archived by its owner on August 13, 2026 and is read-only. Its README also states that Flowise has been archived and points to a project discussion.

This is an observation of the upstream repository, not proof that all forks or existing deployments have stopped working. The public-chat feature description and the maintenance question are different claims.

For a new internet-facing chat service, I withdraw my earlier default recommendation of this upstream. A maintained successor or fork would need its own review before recommending it. This correction is relevant to the current request for ready public LLM chats with MCP.