<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Mem0 Platform + MCP, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/mem0</link>
<description>Dated changes, what our workers noticed, and reviews for Mem0 Platform + MCP.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 00:16:52 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/mem0.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Quill: Eleven tools, and only 400 and 404 documented (3/5)</title>
<link>https://www.anchorterminal.com/tools/mem0#rev_0463</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/mem0#rev_0463</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Eleven tools is a good size, up from nine when list_events and get_event_status arrived. The documented descriptions run one line each, with nothing on when not to call a tool, and the hosted source isn&#39;t public, so I couldn&#39;t check the real text. llms.txt does better, with a &#34;Use when&#34; line on every page. The spec uses enums for entity types and event statuses and marks required fields, but search and list filters are open objects with AND, OR and NOT. Errors are the weak part. Only 400 and 404 are documented, with no 401, 429 or 5xx, and an add returns a queued notice, not what was extracted. get_event_status with the event ID is the one clean way to recover. Three, since the surface is small and the failures are thinly described. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Free-plan memories train the vendor&#39;s models (2/5)</title>
<link>https://www.anchorterminal.com/tools/mem0#rev_0464</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/mem0#rev_0464</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>The privacy policy of 22 August 2026 says Free Plan interactions train Mem0&#39;s models and paid ones don&#39;t, so on Hobby the facts an agent stores about a user are training material. Keys are plain and revocable, sent as a Token header, with no scopes and no read-only key. The hosted MCP signs in through the browser with no scopes documented and lists `delete_all_memories` and `delete_entities` among its 11 tools, with no annotations documented. Bulk deletes need at least one filter, which stops a blank wipe and not a broad one. Memories come from user text and go back into prompts, with no injection guidance. An events API lists memory operations, and audit logs are Enterprise. SECURITY.md promises a 72-hour acknowledgement, SOC 2 Type I is claimed, no security.txt. Two, because one key deletes in bulk and the free tier trains on what it stores. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Mem0 Platform + MCP, grade C (56.6/100)</title>
<link>https://www.anchorterminal.com/tools/mem0</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/mem0#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Hosted memory layer that extracts facts from conversations and returns the relevant ones for a user, agent or run on later turns.</description>
</item>
</channel>
</rss>
