Mem0 Cloud
REMOTE · MEM0-CLOUD.SAASTEMLY.COM
A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):...
Available components
Last scanned (13 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1512 tokens (~378/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_memories" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 3 to 23. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://mem0-cloud.saastemly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=saastemly.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 916a34fd933a20430e4c2b1b81ac507f |
| SANs: saastemly.com, mem0-cloud.saastemly.com, *.mem0-cloud.saastemly.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mem0-cloud.saastemly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| saastemly.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mem0-cloud.saastemly.com/mcp | Verified | 200 | |
| http (plaintext) | http://mem0-cloud.saastemly.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_memory Store memories from a conversation, like mem0's add ~467
Store memories from a conversation, like mem0's add: an AI model extracts durable facts about the user from the messages (or, with infer=false, stores each message as is), embeds them and saves them privately under your memory_key (a secret string you generate; required). Identical facts are stored once. Needs at least one of user_id, agent_id, app_id, run_id. Memories are kept for 365 days. Returns {event_id, status, results:[{id, memory, event: ADD|NONE}]}. Price: $0.008 a call (3 free calls a day without an API key).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Entity: the agent the memories belong to (1-128 characters) |
| app_id | string | – | Entity: the app (1-128 characters) |
| custom_instructions | string | – | Optional extra extraction instructions (with includes and excludes, up to 800 bytes together) |
| excludes | string | – | Optional: what not to extract |
| expiration_date | string | – | Optional YYYY-MM-DD: the memory is hidden from search and listing after that day (unless show_expired is true) |
| includes | string | – | Optional: what to focus on when extracting |
| infer | boolean | – | Default true: extract facts with the model. false: store each message verbatim (up to 10 messages of 300 characters) |
| memory_key | string | yes | Your secret: a random string of 16-256 characters that you generate once and keep (also accepted as the X-Memory-Key header). Memories are stored and searched only under its hash, so nobody who lacks… |
| messages | array | yes | Conversation turns, each {role: user|assistant|system, content: string}; up to 6000 bytes as JSON. A plain string is also accepted (one user message). |
| metadata | object | – | Custom key/value metadata stored with every memory (up to 2000 bytes as JSON) |
| run_id | string | – | Entity: the session or run (1-128 characters) |
| user_id | string | – | Entity: the user the memories are about (1-128 characters) |
No output schema declared.
No examples provided.
delete_memories Delete your stored memories, like mem0's delete memory and delete all memories ~281
Delete your stored memories, like mem0's delete memory and delete all memories. With memory_id: deletes that one memory (404 if it is not yours). Without it: deletes up to 200 of your memories matching user_id, agent_id, app_id or run_id (at least one), and says if more remain. Requires your memory_key (a secret string you generate): other keys cannot delete your memories. Price: $0.002 a call (3 free calls a day without an API key).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Entity: the agent the memories belong to (1-128 characters) |
| app_id | string | – | Entity: the app (1-128 characters) |
| memory_id | string | – | UUID of one memory to delete; leave out to delete by entity instead |
| memory_key | string | yes | Your secret: a random string of 16-256 characters that you generate once and keep (also accepted as the X-Memory-Key header). Memories are stored and searched only under its hash, so nobody who lacks… |
| run_id | string | – | Entity: the session or run (1-128 characters) |
| user_id | string | – | Entity: the user the memories are about (1-128 characters) |
No output schema declared.
No examples provided.
get_memories Read your stored memories, like mem0's get memory and get all memories ~344
Read your stored memories, like mem0's get memory and get all memories. With memory_id: returns that one memory (404 if it is not yours). Without it: returns a page {count, next, previous, results} of the memories matching user_id, agent_id, app_id or run_id (at least one; "*" matches any value), newest first. Requires your memory_key (a secret string you generate): a different key sees nothing. Price: $0.002 a call (3 free calls a day without an API key).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Entity: the agent the memories belong to (1-128 characters) |
| app_id | string | – | Entity: the app (1-128 characters) |
| memory_id | string | – | UUID of one memory to fetch; leave out to list memories instead |
| memory_key | string | yes | Your secret: a random string of 16-256 characters that you generate once and keep (also accepted as the X-Memory-Key header). Memories are stored and searched only under its hash, so nobody who lacks… |
| page | integer | – | Page number, from 1 (default 1) |
| page_size | integer | – | Memories per page, 1-100 (default 50) |
| run_id | string | – | Entity: the session or run (1-128 characters) |
| show_expired | boolean | – | Include memories whose expiration_date has passed (default false) |
| user_id | string | – | Entity: the user the memories are about (1-128 characters) |
No output schema declared.
No examples provided.
search_memories Search your stored memories by meaning, like mem0's search ~324
Search your stored memories by meaning, like mem0's search: embeds the query and returns the closest memories with a relevance score from 0 to 1. Only memories stored under the same memory_key (your secret string; required) are searched. filters must name at least one of user_id, agent_id, app_id, run_id. Returns {results:[{id, memory, score, metadata, ...}]}. Price: $0.004 a call (3 free calls a day without an API key).
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | mem0 filters: at least one of user_id, agent_id, app_id, run_id, each a string, "*" or {"in": [up to 20 strings]}; AND lists of those. OR and NOT are not supported. |
| memory_key | string | yes | Your secret: a random string of 16-256 characters that you generate once and keep (also accepted as the X-Memory-Key header). Memories are stored and searched only under its hash, so nobody who lacks… |
| query | string | yes | What to look for, in natural language (up to 500 characters) |
| show_expired | boolean | – | Include memories whose expiration_date has passed (default false) |
| threshold | number | – | Minimum relevance score, 0-1 (default 0.1; 0 disables) |
| top_k | integer | – | How many memories to return, 1-100 (default 10) |
No output schema declared.
No examples provided.
How do I install the Mem0 Cloud MCP server?
Mem0 Cloud is a hosted endpoint at https://mem0-cloud.saastemly.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mem0-cloud.saastemly.com
claude mcp add --transport http com-saastemly-mem0-cloud 'https://mem0-cloud.saastemly.com/mcp'
What is the Mem0 Cloud MCP server?
Mem0 Cloud is an MCP server listed in the public MCP registry as com.saastemly/mem0-cloud. A hosted agent-memory API shaped like mem0's REST API (an alternative to running mem0 yourself):... This page covers its hosted endpoint (https://mem0-cloud.saastemly.com/mcp).
Is the Mem0 Cloud MCP server safe to use?
Mem0 Cloud scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mem0 Cloud MCP server expose?
Mem0 Cloud exposes 4 tools: add_memory, search_memories, get_memories, delete_memories. Their descriptions and schemas cost roughly 1,416 tokens of context every time the server is loaded.
Does the Mem0 Cloud MCP server require authentication?
No. We connected to Mem0 Cloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mem0 Cloud MCP server still maintained?
Mem0 Cloud is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.