emem, the verifiable memory protocol for the physical world

emem, the verifiable memory protocol for the physical world is a remote MCP server: there is nothing to install. Its endpoint is https://emem.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/vortx-ai/emem:latest. The package starts a local server that speaks MCP over Streamable HTTP; the client then connects to it by URL (the entry names docker as the runtime). It reads these environment variables: PORT, EMEM_BIND, EMEM_DATA, EMEM_PUBLIC_URL and EMEM_TLS_DOMAINS; set them in the client's configuration for this server.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect