The cause of the freeze lies in the last line of the log

[muort521]

json：
[R2 -> App (Message)] {"jsonrpc":"2.0","id":"0f80...","result":{"content":["0x000366c0 entry0",""]}}

The issue stems from the format of content:
The MCP protocol stipulates that content must be an array of objects, such as [{"type": "text", "text": "content..."}].
However, what was actually received was ["0x000366c0 entry0", ""] — which is an array of strings.
This is a bug in the r2mcp tool itself (it took a shortcut when handling list_entrypoints and directly inserted strings). The AI App received a data format it couldn't interpret, causing the parser to crash and the UI to freeze.

[trufae]

actually afaik the protocol specifies that content must be an actual string, if the response is a json it must be passed as an structuredContent in a separate field in the jsonrpc result and this one is actually not supported by all agents, so we are just using the content for now, but you are right, this construction is wrong. fixing now. for some reason i was not notified and missed this issue until now. also i wonder why any agent would accept the current response xD