Universal Memory Protocol Wants to Be MCP for Memory

We've covered four agent-memory products in a week, Supermemory, Hyper, Walrus, MemPalace. Each one stores your agent's memory its own way, which means the moment you switch tools, the memory doesn't come with you. Universal Memory Protocol is the answer to that mess: not another store, a standard. It explicitly wants to do for memory what MCP did for tools and A2A did for agent-to-agent talk.

The shape: signed, portable JSON records with bi-temporal tracking and six operations, recall, remember, revise, forget, get, capabilities. Your memory becomes a portable file you own, encrypted under your own DID, that any compliant agent or vendor can read. Four conformance levels so you can adopt it gradually, and it runs over files, SQL, Redis, or vector databases. It hit the HN front page today.

The honest take: a protocol only matters if people adopt it, and the memory space is crowded with vendors who'd rather lock you in than interoperate. MCP won because Anthropic backed it. UMP is a near-solo effort right now. But the instinct is right, after a year of everyone building their own memory silo, somebody had to propose the portable format. Spec and repo at universalmemoryprotocol.io.