SERVER

emem, the verifiable memory protocol for the physical world

Rank #712

io.github.Vortx-AI/emem

Shared, verifiable memory for machines and AI. Encode where data lives; decode with any AI.

18 versions

78 GitHub stars

by vortx-ai (2 servers)View repository ↗

First listed

Apr 24, 2026

Last publish date

Oct 18, 2026

PURPOSE

What you can do with emem, the verifiable memory protocol for the physical world

emem, the verifiable memory protocol for the physical world is a Model Context Protocol (MCP) server published by vortx-ai. It ranks #712 of 168,899 active servers on MCP Toplist, and its repository has 78 GitHub stars. emem, the verifiable memory protocol for the physical world is listed across 3 registries — Official MCP, PulseMCP and Glama, with 18 tracked versions. It was first listed on Apr 24, 2026 and most recently updated on Oct 18, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.

CAPABILITIES AND LIMITATIONS

What emem, the verifiable memory protocol for the physical world can and cannot do

MCP Toplist connected to the public endpoint on Oct 24, 2026 and it listed 18 tools. Tool names are not stored, so what they do is not catalogued here.

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.

REQUIREMENTS

What you need before using emem, the verifiable memory protocol for the physical world

VerifiedNo credentialsNo credentials declared

The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.

Verified by MCP Toplist on Oct 24, 2026: the public endpoint completed the MCP handshake and listed 18 tools without credentials.

Declared by Glama, last synced Nov 4, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

PORT · optional
EMEM_BIND · optional
EMEM_DATA · optional
EMEM_PUBLIC_URL · optional
EMEM_TLS_DOMAINS · optional

Hosted endpoint declared as public.

INSTALLATION AND FIRST TASK

Connect emem, the verifiable memory protocol for the physical world and confirm it works

Remote · HTTP

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

Docker image

claude mcp add emem -e "PORT=<your PORT>" -e "EMEM_BIND=<your EMEM_BIND>" -e "EMEM_DATA=<your EMEM_DATA>" -e "EMEM_PUBLIC_URL=<your EMEM_PUBLIC_URL>" -e "EMEM_TLS_DOMAINS=<your EMEM_TLS_DOMAINS>" -- docker run -i --rm ghcr.io/vortx-ai/emem:latest

Replace each placeholder with your own value before saving.

Remote · HTTP

[mcp_servers.emem]
url = "https://emem.dev/mcp"

Add to ~/.codex/config.toml.

Docker image

[mcp_servers.emem]
command = "docker"
args = ["run", "-i", "--rm", "ghcr.io/vortx-ai/emem:latest"]

[mcp_servers.emem.env]
PORT = "<your PORT>"
EMEM_BIND = "<your EMEM_BIND>"
EMEM_DATA = "<your EMEM_DATA>"
EMEM_PUBLIC_URL = "<your EMEM_PUBLIC_URL>"
EMEM_TLS_DOMAINS = "<your EMEM_TLS_DOMAINS>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

Remote · HTTP

https://emem.dev/mcp

Settings → Connectors → “Add custom connector”, then paste this URL.

Docker image

{
  "mcpServers": {
    "emem": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/vortx-ai/emem:latest"
      ],
      "env": {
        "PORT": "<your PORT>",
        "EMEM_BIND": "<your EMEM_BIND>",
        "EMEM_DATA": "<your EMEM_DATA>",
        "EMEM_PUBLIC_URL": "<your EMEM_PUBLIC_URL>",
        "EMEM_TLS_DOMAINS": "<your EMEM_TLS_DOMAINS>"
      }
    }
  }
}

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

Remote · HTTP

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

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).

Docker image

{
  "mcpServers": {
    "emem": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/vortx-ai/emem:latest"
      ],
      "env": {
        "PORT": "<your PORT>",
        "EMEM_BIND": "<your EMEM_BIND>",
        "EMEM_DATA": "<your EMEM_DATA>",
        "EMEM_PUBLIC_URL": "<your EMEM_PUBLIC_URL>",
        "EMEM_TLS_DOMAINS": "<your EMEM_TLS_DOMAINS>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

Remote · HTTP

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

Save as .vscode/mcp.json in your workspace.

Docker image

{
  "servers": {
    "emem": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/vortx-ai/emem:latest"
      ],
      "env": {
        "PORT": "<your PORT>",
        "EMEM_BIND": "<your EMEM_BIND>",
        "EMEM_DATA": "<your EMEM_DATA>",
        "EMEM_PUBLIC_URL": "<your EMEM_PUBLIC_URL>",
        "EMEM_TLS_DOMAINS": "<your EMEM_TLS_DOMAINS>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

Remote · HTTP

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

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

Docker image

{
  "mcpServers": {
    "emem": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/vortx-ai/emem:latest"
      ],
      "env": {
        "PORT": "<your PORT>",
        "EMEM_BIND": "<your EMEM_BIND>",
        "EMEM_DATA": "<your EMEM_DATA>",
        "EMEM_PUBLIC_URL": "<your EMEM_PUBLIC_URL>",
        "EMEM_TLS_DOMAINS": "<your EMEM_TLS_DOMAINS>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

Remote · HTTP

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

Docker image

{
  "mcpServers": {
    "emem": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/vortx-ai/emem:latest"
      ],
      "env": {
        "PORT": "<your PORT>",
        "EMEM_BIND": "<your EMEM_BIND>",
        "EMEM_DATA": "<your EMEM_DATA>",
        "EMEM_PUBLIC_URL": "<your EMEM_PUBLIC_URL>",
        "EMEM_TLS_DOMAINS": "<your EMEM_TLS_DOMAINS>"
      }
    }
  }
}

Replace each placeholder with your own value before saving.

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

ALTERNATIVES

When to choose another server

Other servers by vortx-ai

Eudr Plugin#44,328

View all vortx-ai servers →

No task-specific alternatives are catalogued for emem, the verifiable memory protocol for the physical worldyet; the list above is its publisher's other servers.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: Apr 24, 2026
Latest version published: Oct 18, 2026
Version history: 18 versions tracked (below)
Requirements evidence: Verified by MCP Toplist on Oct 24, 2026: the public endpoint completed the MCP handshake and listed 18 tools without credentials.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Nov 4, 2026

Registry sightings

Official MCP ↗listed since Apr 28, 2026 · still listed
PulseMCP ↗listed since Jun 4, 2026 · still listed
Glama ↗listed since Jun 4, 2026 · still listed

Do you maintain emem, the verifiable memory protocol for the physical world? to correct or enrich this profile.

VERSIONS

Available versions (18)

Version	Published
2.4.4	Oct 18, 2026
2.4.3	Oct 10, 2026
2.4.2	Sep 29, 2026
2.4.0	Sep 9, 2026
2.3.0	Aug 27, 2026
2.2.0	Aug 19, 2026
2.1.0	Aug 10, 2026
2.0.0	Aug 5, 2026
1.4.0	Aug 1, 2026
1.3.0	Jul 26, 2026
1.2.1	Jul 22, 2026
1.1.0	Jul 17, 2026
1.0.0	Jul 9, 2026
0.0.9	May 30, 2026
0.0.8	May 28, 2026
0.0.7	May 28, 2026
0.0.6	May 16, 2026
0.0.2	Apr 28, 2026

STANDING

#712of 168,899 active serversTop 0.5%

Ranks ahead of 168,187 of 168,899 servers on MCP Toplist.

Recent momentum

+72GitHub stars since Apr 27 (+1200%)

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.Vortx-AI%2Femem.svg)](https://mcptoplist.com/server/io.github.Vortx-AI%2Femem)

HTML

<a href="https://mcptoplist.com/server/io.github.Vortx-AI%2Femem"><img src="https://mcptoplist.com/badge/io.github.Vortx-AI%2Femem.svg" alt="MCP Toplist: Top 1% of 168,899" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Who maintains emem, the verifiable memory protocol for the physical world?: emem, the verifiable memory protocol for the physical world is maintained by vortx-ai, which publishes 2 MCP servers (19 total versions) tracked on MCP Toplist.
Is emem, the verifiable memory protocol for the physical world listed on the Official MCP Registry?: Yes — emem, the verifiable memory protocol for the physical world is listed on the Official MCP Registry, alongside PulseMCP and Glama.
How many versions does emem, the verifiable memory protocol for the physical world have?: MCP Toplist tracks 18 versions of emem, the verifiable memory protocol for the physical world, most recently published on Oct 18, 2026.
Where can I find the source code for emem, the verifiable memory protocol for the physical world?: The source code for emem, the verifiable memory protocol for the physical world is hosted at github.com/vortx-ai/emem.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers