emem

emem is an open-source (Apache-2.0) shared memory protocol and hosted responder from Vortx AI. It lets files, Earth observations, agent notes and device traces be named by short content-addressed tokens and signed with Ed25519, so any AI agent can resolve and check them without trusting the sender. It is exposed over MCP, REST and A2A, with Python and TypeScript clients and a self-hostable Rust server.

What It Is

emem splits trust into encoding and decoding. A source such as a file server, lab, camera or device hashes what it holds into units and signs a small record; the bytes stay where they are. Any model resolves the token back to that record, checks the signer and proves that one unit belongs to the whole. Token kinds include emem:fact (one signed observation), emem:bundle (a set of facts), emem:tree (a file as a signed Merkle root over its units), emem:entity (an object identity), emem:state, emem:trace and raster types.

How the workflow runs

An agent connects to the MCP endpoint, which advertises an 18-tool core loop by default, with 115 tools available in total. It resolves a place to a roughly 10 m cell, recalls signed measurements (for example elevation or NDVI from open archives such as ESA, NASA, USGS and JRC), and receives an Ed25519 receipt that verifies offline or at the /verify page. Agent-written notes live in a writable memory with attester-bound namespaces, supersession and contradiction scoring across writers. Reads accept bi-temporal bounds so an auditor can replay what was known on a given date.

Verification and audit

Everything signed enters an append-only RFC 6962 Merkle transparency log, with signed heads, inclusion and consistency proofs and independent witness co-signatures. emem-guard checks citations in a draft and returns allow or deny with a reason. The docs state that a signature shows who signed, not that a value is true.

Where it fits

Documented use cases include shared memory between agents, EUDR due-diligence statements, carbon-project review, flood-exposure pre-screening and checking declared origins. The emem-airgap encoder takes custody of files on machines with no network. It can be self-hosted with Docker, and the project is listed in several MCP and plugin directories.