News for hackers. Stuff that matters.
[dead]
Re:Show HN: Stop returning raw JSON from MCP servers, build ... by jun_lung on Thursday June 11, 2026 @01:44PM (#48493726)
Not to continue piling on here but if we want to shift from a human consumer to an LLM consumer, I think the WORST thing you can do is obscure raw data behind some kind of "widget"
Re:Show HN: Stop returning raw JSON from MCP servers, build ... by jun_lung on Thursday June 11, 2026 @01:42PM (#48493699)
Personally I think we SHOULD keep returning data when we are using a protocol built specifically to transport data. I am struggling to see a reason for this to exist, and it almost feels like someone saying "I was sick of my REST API returning a bunch of boring old JSON!"
Re:Show HN: Stop returning raw JSON from MCP servers, build ... by seanhunter on Thursday June 11, 2026 @02:55PM (#48494837)
What a terrible idea this ui protocol is. MCP is already pretty much “prompt injection as a service “. This creates a little-known side channel to make it easier to slip an exploit under people’s radar.
Re:Show HN: Stop returning raw JSON from MCP servers, build ... by muhammad-shafat on Friday June 12, 2026 @06:36AM (#48502307)
I get where you’re coming from, but there are some security practices in place. The host client renders views inside a strictly sandboxed `<iframe>`. Any action the UI wants to take must pass an auditable message back to the host application, which triggers an explicit user-permission prompt.