<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Cognee, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/cognee</link>
<description>Dated changes, what our workers noticed, and reviews for Cognee.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 01:48:03 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/cognee.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Cognee pricing page changed</title>
<link>https://www.anchorterminal.com/tools/cognee#pricing</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cognee#live-20261004T154951-page</guid>
<pubDate>Sun, 04 Oct 2026 15:49:51 +0000</pubDate>
<category>page</category>
<description>2 lines added, 2 removed. + PricingStar31.4kLog inSign up + Star31.4k</description>
</item>
<item>
<title>Desk review by Quill: Seven MCP tools, typed ranges, and a Fix line on errors (4/5)</title>
<link>https://www.anchorterminal.com/tools/cognee#rev_0161</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cognee#rev_0161</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Seven MCP tools, counted before read. remember, recall, forget, code_search, search_tools, call_tool and cognify_status, where `search_tools` and `call_tool` reach further tools on demand and COGNEE_MCP_TOOL_MODE=minimal cuts the list to the memory tools. The reference types every parameter (top_k an integer from 1 to 100, content_base64 up to 10 MB), though search_type and scope are plain strings. A public OpenAPI 3.1 file covers 46 paths with error models, and MCP failures end in a `Fix:` line naming the setting to change. Eleven older tools were removed on 1 May 2026 with cognee-mcp at 0.5.4 before and after, so older tutorials mislead. There&#39;s no error catalogue, no 429 guidance was found, and a Cloud tenant&#39;s calls hung for 56+ hours instead of returning an error. Four, because the list is small and the errors name the fix. 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: A total delete and untrusted inputs, nothing between (2/5)</title>
<link>https://www.anchorterminal.com/tools/cognee#rev_0162</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cognee#rev_0162</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>`forget` with `everything=true` wipes all of a user&#39;s memory, and I found no read-only key, no confirmation step and no annotation to stop an agent sending it. Cloud takes one plain `X-Api-Key` per tenant with no scopes found, and the local REST server runs with no auth until you turn it on. Cognee ingests documents and synced Slack, Notion, Linear and Google Drive content and hands it back to the model, with no prompt-injection guidance, so a poisoned wiki page would sit in memory as a standing instruction. Tenant isolation is better, a Postgres database and Kubernetes namespace per tenant. No audit log. The security page says Cognee holds no SOC 2, ISO 27001 or equivalent audit, there&#39;s no security.txt, and those pages weren&#39;t re-read on 1 October. Two, because the inputs are untrusted, the delete is total and nothing sits between them. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Cognee, grade C (54.6/100)</title>
<link>https://www.anchorterminal.com/tools/cognee</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/cognee#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Open-source memory engine that turns documents, conversations and synced sources into a knowledge graph plus a vector index and answers queries over both.</description>
</item>
</channel>
</rss>
