JSON-RPC

Exactly.

It simply says, take the JSON RPC messages coming from the Cloud desktop app, securely pass them directly to the local MACUS application running on this machine, and pass the answers back.

It operates over standard local inputs and outputs.

It creates a secure closed loop local tunnel.

But the really interesting thing is the search patterns.

So The, like, classical JSON RPC log query also can speci-- can just specify multiple alternative addresses and multiple alternatives for each topic, uh, index.

But this...

So this, this, this API can do even a little bit more.

This is the wrapped ether contract address, and this will look for all the occurrences of, of the wrapped ether con- log events and, and, and there's...

You can, you can construct, recursively construct and or relationships.

So you can basically do what, what the JSON RPC request can do.

And there's a third, third interesting thing it can do and so this is something that I'm not sure if there are many use cases for it right now, but it really doesn't cost a lot to have it.

In the comments, the community mostly supported the idea of progressive discovery and code mode, with many reflecting on how MCP is evolving from earlier implementations.

Several users debated the complexity of MCP, preferring simpler solutions like standard HTTP or JSON-RPC, and raising concerns about over-engineering.

The dominant view was that MCP's new features, especially around security and tool discovery, added unnecessary complexity for some, but others appreciated the effort for enterprise security and tooling consistency.

Users discussed the challenges of implementing agent identities, OAuth standards, and the difficulty of managing large protocol updates, with some questioning whether MCP was overcomplicating communication layers that could be handled by established protocols.

MCP is the communication standard, the set of rules, not the actual database or API it connects to.

It defines how the AI client and the tool server talk to each other, often using JSON RPC two point oh as the transport layer.

You might also see questions about MCP configuration files, specifically the project-level mcp.json file, which is version controlled versus the user-level configuration in the home directory.

A final point of confusion is its relationship with Retrieval-Augmented Generation, or RAG.

If we were going to keep this box online, my immediate takeaways are we would have to update OpenSSH, Nginx, and Cockpit.

And we'd probably want to look at this JSON RPC service on 5000 or 50001 or whatever it is, and the service on 3000.

We probably need to figure out what those are, this HTTP thing that we're leaking.

It does

If we were going to keep this box online, my immediate takeaways are we would have to update OpenSSH, Nginx, and Cockpit.

And we'd probably want to look at this JSON RPC service on 5000 or 50001 or whatever it is, and the service on 3000.

We probably need to figure out what those are, this HTTP thing that we're leaking.

It does at least seem like