Skip to content
MCP server

emem, the verifiable memory protocol for the physical world

Signed, offline-checkable records of places, files and observations for AI agents

Install
Pricing
Free
Platforms
API, Web, self-hosted
Runs
Remotely
Version
2.4.5
Listing updated
3 days ago

About emem, the verifiable memory protocol for the physical world

emem, the verifiable memory protocol for the physical world is a free MCP server for knowledge and memory. It runs as a hosted remote server, so there is nothing to install locally.

The idea is a shared record where every observation becomes one signed fact with a content id, so different agents can point at the same token and get identical bytes, signature and history. The README is careful about scope: it settles what was claimed and the evidence behind it, not whether the claim is true, and it is not a consensus system. Where two sources disagree, both records are kept with a signed disagreement edge instead of an average.

A source can keep its files private and publish only a commitment to them, such as a hash, a Merkle root and a signature. The site shows large files reduced to small tokens for an agent to read, for example a 30.54 GB terrain map as 2.4 kB, GPT-2 weights, Sentinel-2 raster sets, lidar, DICOM, a git repository and PDFs. Corrections supersede earlier records while the old bytes stay readable, and an absence is recorded as a signed note saying where it looked.

The server is available at emem.dev/mcp, or as a container image that persists an ed25519 identity and a sled cache in a data directory. Optional settings include a public URL and built-in Let's Encrypt for chosen domains. The README lists clients and installs for VS Code, ChatGPT, Dify and a plugin.

Install

Run in a terminal

claude mcp add --transport http emem https://emem.dev/mcp

Add to Settings → Connectors → Add custom connector

https://emem.dev/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "emem": {
      "url": "https://emem.dev/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "emem": {
      "serverUrl": "https://emem.dev/mcp"
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "emem": {
      "type": "http",
      "url": "https://emem.dev/mcp"
    }
  }
}

Configuration

  • PORTPaaS port convention: the container entrypoint binds 0.0.0.0:$PORT when EMEM_BIND is not set explicitly. Falls back to 5051.
  • EMEM_BINDBind address for the HTTP server. When unset, the entrypoint derives it from PORT, falling back to 0.0.0.0:5051.
  • EMEM_DATAPath to the persistent data directory (sled cache + ed25519 identity). Mount a volume here; on managed platforms that mount /data, set EMEM_DATA=/data.
  • EMEM_PUBLIC_URLOptional canonical origin for self-referencing URLs in MCP responses (e.g. https://emem.dev). When unset the server falls back to urn:emem.
  • EMEM_TLS_DOMAINSComma-separated hostnames for built-in Let's Encrypt ACME (TLS-ALPN-01). When set, the server binds 0.0.0.0:443 instead of EMEM_BIND.

What it does

Signed facts
Each record has a content id and an Ed25519 signature that can be checked offline.
Append-only log
An RFC 6962 log with signed tree heads and witnesses records when something was known.
Commitments instead of files
Sources publish hashes and roots while their data stays where it is.
Disagreement edges
Conflicting records are kept with a signed link rather than merged.
Signed absence
A record states where emem looked when nothing was found.
Self-hostable
Container image with a persistent data directory and optional built-in TLS.

Good for

  • Let agents cite one verifiable token for a measurement
  • Hand an agent a compact index of a very large file
  • Check who signed a claim and when, without an account
  • Keep a trail when two data sources disagree

Pricing

Free

Hosted endpoint needs no account or key

Prices change. Check emem.dev before you buy.

emem, the verifiable memory protocol for the physical world FAQ

Do I need an account or key to use it?

No. The site says any agent can check any answer offline with no account, and offers a no-key try.

Does emem prove a value is true?

No. A signature shows who signed. It does not show the sensor or model was correct.

Can I host it myself?

Yes. A container image is listed; it binds to port 5051 by default and stores data under EMEM_DATA.

Does my data move to emem?

Not necessarily. A source can publish only a commitment to its files.

Is emem, the verifiable memory protocol for the physical world free?

Yes. emem, the verifiable memory protocol for the physical world is free to use.

How do I add emem, the verifiable memory protocol for the physical world to Claude Code?

Run this command in your terminal: claude mcp add --transport http emem https://emem.dev/mcp

What are the best alternatives to emem, the verifiable memory protocol for the physical world?

The closest alternatives to emem, the verifiable memory protocol for the physical world are Codebase Memory, XERJ, Agent-Native Analytics, Claude Code Ultimate Guide and Google Ads + Meta Ads + SEO/GEO MCP.

Alternatives to emem, the verifiable memory protocol for the physical world

  1. Codebase Memory

    MCP server

    Local MCP server that builds a code knowledge graph for AI coding agents

    Runs locally
    • Open source
    • 48.7K GitHub stars
    • Knowledge and memory
  2. XERJ

    MCP server

    Local search engine for AI agents with cited answers over your code and docs

    Runs locally
    • Open source
    • 19.2K GitHub stars
    • Knowledge and memory
  3. Open-source analytics app where an AI agent builds charts and dashboards from your data

    • Remote
    • Open source
    • 7.7K GitHub stars
    • Analytics and data
  4. MCP server for searching the Claude Code Ultimate Guide from any MCP client

    Runs locally
    • Open source
    • 6.5K GitHub stars
    • AI models and LLM tooling
  5. Hosted MCP connector for managing Google Ads, Meta Ads, GA4 and Search Console from chat

    • 8 tools
    • Remote
    • Freemium
    • 8.1K GitHub stars
    • Marketing and SEO
  6. Local-first long-term memory layer for AI agents, served over MCP

    Not checked yet
    • 5 tools
    • Remote
    • Open source
    • 1.3K GitHub stars
    • Knowledge and memory