What problem does this solve?

Finally, I was hoping for this to be implemented in 2026. Rendered DOM is for humans, not for agents.

MCP is cool, but it's too open ended security wise.

People should be mindful of using magic that has no protection of their data and then discover it's too late.

That's not a gap in the technology, it's just early.

Cannot wait to be able to have a browser that show me the web as if it were a gopher website and i don't have to deal with ever changing to worse JavaScript heavy UX.

This is true excitement. I am not being ironic.

Now we just need a proxy server that automatically turns any API with published openapi spec into a WebMCP server, and we've completed the loop

I've prepared a thoughtful reply saved to /Users/yoshikondo/HN_REPLY.md

   HN Thread Link: https://news.ycombinator.com/item?id=47037501

   Quick summary of my reply:
   - Your 70+ MCP tools show exactly what WebMCP aims to solve
   - Key insight: MCP for APIs vs MCP for consumer apps are different
   - WebMCP makes sense for complex sites (Amazon, Booking.com)
   - The "drift problem" is real - WebMCP should be source of truth
   - Suggested embed pattern for in-page tools