Back to Browse

Emem MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://emem.dev/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

18 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

PaaS port convention: the container entrypoint binds 0.0.0.0:$PORT when EMEM_BIND is not set explicitly. Falls back to 5051.Optional

Environment variable: PORT

Bind address for the HTTP server. When unset, the entrypoint derives it from PORT, falling back to 0.0.0.0:5051.Optional

Environment variable: EMEM_BIND

Path to the persistent data directory (sled cache + ed25519 identity). Mount a volume here; on managed platforms that mount /data, set EMEM_DATA=/data.Optional

Environment variable: EMEM_DATA

Optional canonical origin for self-referencing URLs in MCP responses (e.g. https://emem.dev). When unset the server falls back to urn:emem.Optional

Environment variable: EMEM_PUBLIC_URL

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.Optional

Environment variable: EMEM_TLS_DOMAINS

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-vortx-ai-emem": {
      "env": {
        "PORT": "your-port-here",
        "EMEM_BIND": "your-emem-bind-here",
        "EMEM_DATA": "your-emem-data-here",
        "EMEM_PUBLIC_URL": "your-emem-public-url-here",
        "EMEM_TLS_DOMAINS": "your-emem-tls-domains-here"
      },
      "url": "https://emem.dev/mcp"
    }
  }
}

Reviews

No reviews yet

Be the first to review this server!