mcpbeat Sign in

DeepMem MCP Server

by deepmemteam Your server? Claim it
not responding

DeepMem is listed as active in the registry but did not answer our last check. It exposes 2 tools. Last commit 17 Aug 2026.

Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.

Uptime history 80 days of history · worst day 0%
80 days agonow
0.0%
Uptime 24h
0 of 92 checks
2
Tools
read from the server
19457 ms
Response time
average over 24h
114
Stars
last commit 17 Aug 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 September 2026. No other catalogue keeps this.

1 Sep a tool changed version

DeepMem does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add deepmem --transport http https://deepmem.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://deepmem.dev/mcp
~/.codex/config.toml
[mcp_servers.deepmem]
url = "https://deepmem.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "deepmem": {
      "url": "https://deepmem.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "deepmem": {
      "type": "http",
      "url": "https://deepmem.dev/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

deepmem
deepmem_search
Search memories stored in DeepMemory using semantic search. Returns the most relevant memories for the given query, ranked by hybrid scoring (vector similarity + BM25 keyword match + entity boost + time decay). Use this to retrieve context from past conversations before responding to the user. Memories are scoped to the user_id provided during write.
deepmem_write
Write conversation messages to DeepMemory for fact extraction and persistent storage. Messages are processed by an LLM to extract structured memories, which are then embedded and stored in a vector database for later semantic search. Set infer=True to enable LLM fact extraction (produces richer memories but costs one LLM call). Set infer=False to store raw messages without extraction. Returns a list of memory IDs for successfully stored facts.

Endpoints

URLTransportStateLatencyChecked
https://deepmem.dev/mcp streamable-http answering 19457 ms 3 min ago

Alternatives to DeepMem

same job, measured the same way
Memanto
by moorcheh-ai

MCP server for Memanto - persistent semantic memory for any MCP-compatible agent

339 installs/wk local only
Memdata
by thelabvenice

Persistent memory for AI agents. Store context, retrieve it semantically.

47 installs/wk local only
Iranti
by nfemmanuel

Persistent, shared memory for AI agents — facts, checkpoints, semantic search.

180 installs/wk local only
repo-memory-mcp
by umarjaum

Persistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.

137 installs/wk local only
memex
by ayushagrawal288

Persistent memory for AI agents — semantic + recency search, ONNX embeddings, Docker Compose.

local only
YourMemory
by sachitrafa

Persistent memory for AI agents. Memories decay with time and strengthen on recall.

376 installs/wk local only
Kirok Memory
by tadfuji

Persistent memory for AI agents - hybrid semantic + keyword recall with autonomous consolidation

147 installs/wk local only
Montycat MCP - Shared Memory for AI Agents
by montygovernance

Shared, persistent memory for AI agents, with semantic recall and live updates.

221 installs/wk local only

DeepMem — questions

Answers built from our own checks of this server.

What can DeepMem do?
It exposes 2 tools, read directly from the server on our last check. Among them: deepmem_search, deepmem_write. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is DeepMem working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 19457 ms. The bar chart above shows every period we have measured.
The registry lists DeepMem as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect DeepMem?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does DeepMem need an API key?
No. DeepMem completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
Is DeepMem open source?
The code is open source: it is published under the MIT licence, written in Python, 114 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at deepmem.dev, which runs on its operator's own terms.