# emem, the verifiable memory protocol for the physical world

emem connects AI agents to verifiable shared memory without moving raw files. It is useful when a model needs to validate data authenticity against cryptographic proofs while bytes stay local.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 74
- Author: Vortx-AI
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Vortx-AI/emem
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/emem-the-verifiable-memory-protocol-for-the-physical-world

## What it does

The server operates over HTTP at `https://emem.dev/mcp`. Rather than uploading complete private datasets or documents to an AI provider, emem keeps files on their host system. Only cryptographic commitments travel outward: BLAKE3 hashes folded into Merkle roots, content identifiers, and author signatures.

Any compatible agent uses compact tokens to locate signed records and verify specific units without reading unshared sections. Fetching existing records or registered open archives requires no account and no API key. Offline verification of your own local trees depends on Python and the included `tree_proof.py` script.

Cryptographic verification proves that bytes were present in the signed file, not that the claims inside that file are accurate. For derived values, the protocol pins the algorithm by its `code_cid` hash rather than running unverified private code in a sandbox.

## Requirements
- Needs: Docker
- Remote server: `https://emem.dev/mcp`
- Environment variables: `PORT`, `EMEM_BIND`, `EMEM_DATA`, `EMEM_PUBLIC_URL`, `EMEM_TLS_DOMAINS` — keys and tokens: ask the human for the values, never commit them or put them in shared files.

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http emem https://emem.dev/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add emem-the-verifiable-memory-protocol-for-the-physical-world --url https://emem.dev/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "emem-the-verifiable-memory-protocol-for-the-physical-world": {
            "url": "https://emem.dev/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "emem-the-verifiable-memory-protocol-for-the-physical-world": {
            "type": "http",
            "url": "https://emem.dev/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http emem-the-verifiable-memory-protocol-for-the-physical-world https://emem.dev/mcp
```

## When to use it
- Verify specific file chunks without uploading full documents to an LLM
- Resolve signed measurements from open Earth archives via cryptographic tokens
- Prove local data integrity using BLAKE3 hashes and Merkle tree roots
- Bind computed outputs to exact code versions using cryptographic hashes

## Example prompts
- Check the emem token for this record and verify it against index.md
- Fetch the elevation measurement for Cairo from the copdem30m archive using emem
- Help me verify the row.json proof against the LICENSE file using tree_proof.py

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md