emem, the verifiable memory protocol for the physical world

io.github.Vortx-AI/emem

About emem, the verifiable memory protocol for the physical world

emem, the verifiable memory protocol for the physical world is an MCP server published by the GitHub account Vortx-AI. Shared, verifiable memory for machines and AI. Encode where data lives; decode with any AI.

It runs on your own machine: your AI client starts it from the Docker (OCI) package ghcr.io/vortx-ai/emem:latest, with no version pinned, or you can connect to the hosted version instead.

It asks for no keys or passwords.

Version 2.4.4 was published on 18 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 10 automated checks on the registry entry and the live tool descriptions: 5 pass, 1 warn, 0 fail, 4 info. How we check.

What it asks for

VariableRequiredSecretDescription
PORTNoNoPaaS port convention: the container entrypoint binds 0.0.0.0:$PORT when EMEM_BIND is not set explicitly. Falls back to 5051.
EMEM_BINDNoNoBind address for the HTTP server. When unset, the entrypoint derives it from PORT, falling back to 0.0.0.0:5051.
EMEM_DATANoNoPath 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_URLNoNoOptional 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_DOMAINSNoNoComma-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.

Checks

CheckResultDetail
Source repository linkedPasshttps://github.com/Vortx-AI/emem
Version pinnedWarnNot pinned: ghcr.io/vortx-ai/emem:latest
Remote uses HTTPSPassAll remote endpoints use https://
Secrets requestedInfoAsks for no secrets
Known package registryPassAll packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownershipInfoName verified via GitHub account Vortx-AI
Registry text aimed at the AIPassDescription and settings contain no hidden characters or instructions to the AI
Code red flagsInfooci packages are not read yet
Tool descriptions readInfoLists 18 tools: emem_entity, emem_locate, emem_recall, emem_memory_token, emem_memory_token_resolve, emem_verify_receipt, emem_memory_contradictions, emem_guard_verdict, emem_tools, emem_ask, search, fetch, …
Hidden instructions in toolsPassRead every tool description and the server instructions: no hidden characters or instructions to the AI

Popularity & health: 53 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity14 / 40

77 GitHub stars, no download count, 2 Hacker News posts (6 points). Best two of the three, each on a log scale.

Activity15 / 25

Last push 2026-10-28, last release 2026-10-18, 0 commits in 90 days.

Issue health8 / 15

8 closed of 8 issues, too few to judge. No data, so half marks.

Our checks16 / 20

1 warning, each costing a fifth.

12 forks, 12 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

2 Hacker News threads linking to the source code. We link to them and copy nothing.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry nameio.github.Vortx-AI/emem
PublisherGitHub account Vortx-AI
How the name is verifiedName verified via GitHub account Vortx-AI. The registry ties the name prefix to that account or domain; it does not check the code.
TypeLocal package and a hosted remote
Packagesoci ghcr.io/vortx-ai/emem:latest no version given (streamable-http)
Remote endpointsstreamable-http https://emem.dev/mcp
Version2.4.4
Published
Last updated
Source repositoryhttps://github.com/Vortx-AI/emem
Websitehttps://emem.dev
CategoryProductivity & notes (assigned by keyword rule, not by hand)

Related servers in Productivity & notes