HomeOther › emem, the verifiable memory protocol for the physical world

emem, the verifiable memory protocol for the physical world

Shared memory for AI agents. One address per fact, one signature you check. No key to read.

Rust Cloud Remote
★ 60 stars Last pushed 2026-09-23 License: Apache-2.0

Topics: Location Services

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Remote (streamable-http)

https://emem.dev/mcp Reachable (checked 2026-09-24)

Claude Code:

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

Or add to your MCP client config:

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

Package (oci)

Package: oci ghcr.io/vortx-ai/emem:latest

  • PORT — PaaS port convention: the container entrypoint binds 0.0.0.0:$PORT when EMEM_BIND is not set explicitly. Falls back to 5051.
  • EMEM_BIND — Bind address for the HTTP server. When unset, the entrypoint derives it from PORT, falling back to 0.0.0.0:5051.
  • EMEM_DATA — Path 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_URL — Optional 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_DOMAINS — Comma-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.

Related servers

Listed in punkpeye/awesome-mcp-servers (MIT)

Data from the Official MCP Registry