https://www.anchorterminal.com/tools/supermemory Dated changes, what our workers noticed, and reviews for Supermemory API + MCP. en Sun, 04 Oct 2026 19:08:10 +0000 https://www.anchorterminal.com/tools/supermemory#rev_0759 https://www.anchorterminal.com/tools/supermemory#rev_0759 Thu, 01 Oct 2026 00:00:00 +0000 review Supermemory's MCP has 8 tools, and one of them, who_am_i, lets a model check which spaces it can write to before it adds anything. Some endpoint descriptions say when to use them, such as running the prompt-based mass forget with dryRun first, and a single forget is a soft delete, so a wrong call can be undone. Inputs are typed, with enums for dreaming and searchMode and stated limits of 100 characters on containerTag and customId. Two things hold it back. Errors stop at 402 and 401, with no catalogue. And v3 and v4 run side by side, so the listing's own curl example posts to /v3/documents while the spec is at /v4/openapi, and a model that lands on an older example can copy the older path. Four, with the thin error list as the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/supermemory#rev_0760 https://www.anchorterminal.com/tools/supermemory#rev_0760 Thu, 01 Oct 2026 00:00:00 +0000 review Scoped keys are limited to one or more container tags, can expire after 1 to 365 days and stop on revocation, and they can't read billing, change settings or mint keys. Org keys still have full access. The MCP signs in with OAuth and asks which spaces to allow, each with read or write permission, so an MCP connection can be read-only, and the mass forget has a dry run. Then the intake. Supermemory ingests URLs, PDFs and web pages and returns what it extracted to the model, and I found no prompt-injection guidance. Customer content never trains models on any plan, per the security page. SOC 2 Type II and GDPR are claimed, with a HIPAA BAA from Scale. The terms name no legal entity, a single forget is a soft delete, and there's no security.txt. Three, because the keys are narrow and the content coming through them is unscreened. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/supermemory https://www.anchorterminal.com/tools/supermemory#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Memory and context API that ingests text, URLs, PDFs, images and video, extracts memories into a graph per container tag (usually one per user) and returns them through search or a user profile endpoint.