mcp-registry/io.github.deepmemteam/deepmem · v1.29.1
As of 2026-10-19 02:39 UTC, the Deepmemteam Deepmem MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.
Claude Code
claude mcp add --transport http deepmemteam-deepmem-mcp-server https://deepmem.dev/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"deepmemteam-deepmem-mcp-server": {
"type": "http",
"url": "https://deepmem.dev/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~2,031 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.deepmemteam%2Fdeepmem/fixes
{
"name": "deepmem_search",
"description": "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).\n\nUse this to retrieve context from past conversations before responding to the user. Memories are scoped to the user_id provided during write.",
"inputSchema": {
"type": "object",
"title": "deepmem_searchArguments",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"title": "Query"
},
"top_k": {
"type": "integer",
"title": "Top K",
"default": 10
},
"api_key": {
"type": "string",
"title": "Api Key",
"default": ""
},
"user_id": {
"type": "string",
"title": "User Id",
"default": "default"
},
"threshold": {
"type": "number",
"title": "Threshold",
"default": 0.3
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "deepmem_write",
"description": "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.\n\nSet infer=True to enable LLM fact extraction (produces richer memories but costs one LLM call). Set infer=False to store raw messages without extraction.\n\nReturns a list of memory IDs for successfully stored facts.",
"inputSchema": {
"type": "object",
"title": "deepmem_writeArguments",
"required": [
"messages"
],
"properties": {
"infer": {
"type": "boolean",
"title": "Infer",
"default": true
},
"run_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Run Id",
"default": null
},
"api_key": {
"type": "string",
"title": "Api Key",
"default": ""
},
"user_id": {
"type": "string",
"title": "User Id",
"default": "default"
},
"agent_id": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Agent Id",
"default": null
},
"messages": {
"type": "array",
"items": {
"type": "object",
"additionalProperties": true
},
"title": "Messages"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.deepmemteam/deepmem"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.deepmemteam/deepmem"}) over MCP.
deepmem_write ~295 tokensdeepmem_search ~219 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.deepmemteam%2Fdeepmem?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.deepmemteam%2Fdeepmem?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.deepmemteam%2Fdeepmem.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.deepmemteam%2Fdeepmem.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.deepmemteam%2Fdeepmem?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2f41a3044c7527a2…, first seen 2026-10-17, included at leaf 485 of 24,438. Version history · verify what your client received.
Compare: most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 02:39 UTC, the Deepmemteam Deepmem MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Deepmemteam Deepmem MCP server advertises 2 tools, including deepmem_search, deepmem_write.
Point your MCP client at this streamable-http endpoint: https://deepmem.dev/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.