May 16, 2026
Click here for chaos
MCP Hello Page
Users kept clicking the wrong link, and the comments turned it into a spec war
TLDR: A developer stopped a flood of “this link is broken” complaints by showing confused visitors a helpful page instead of a scary error. Commenters loved the common-sense fix, but also dragged the messy AI standard behind it and argued over whether users were confused—or the design was.
A tiny website fix has somehow become catnip for comment-section drama. The original post is simple enough: a company launched a server link for AI tools, customers kept opening it in a browser, saw a scary “Unauthorized” message, and instantly assumed the whole thing was broken. So the developer added a friendly web page that basically says, “Hey, this link isn’t for humans, paste it into your app instead.” Result? Support tickets fell off a cliff and customer service finally got to breathe again.
But the real entertainment is in the replies, where people split into camps almost immediately. One side was basically yelling, “This isn’t hacky, this is just how the web works!” Multiple commenters praised the fix as a smart, humane touch, with one calling it the kind of tiny convenience the internet needs more of. Another even joked that it might save users who drop the link into an AI assistant and let the bot explain their mistake back to them.
Then came the spec rage. One frustrated commenter declared they “hate the MCP rules so much,” turning the thread into a mini roast of yet another fast-moving AI standard that seems to confuse normal people on contact. But the sharpest pushback came from a usability scold: if the link was clickable, why blame users for clicking it? In other words, was this a clever rescue mission, or a problem created by bad design in the first place? The comments couldn’t resist turning a boring support fix into a full-on who’s really at fault here? showdown.
Key Points
- •HybridLogic launched an MCP server for its primary work tool and encountered repeated customer reports that the server was not working.
- •The reported problem was caused by users opening the MCP endpoint in a browser and seeing a 401 Unauthorized JSON response.
- •The article says building separate connectors or plugins for every LLM client would be slow and difficult, especially with customers creating internal clients.
- •HybridLogic implemented a conditional response on `GET /mcp` that returns an explanatory HTML page when the request appears to come from a browser.
- •The company reports that the change sharply reduced support tickets, improved customer setup speed, and produced no observed negative impact.