# Context Mode Engine vs Memori

> Context Mode Engine scores 54.6 (C) to Memori's 44.2 (E) for memory search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/context-mode-vs-memori
- Markdown: https://www.anchorterminal.com/compare/context-mode-vs-memori.md (~4,400 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Context Mode Engine scores 54.6 (C) on agent readiness against Memori's 44.2 (E), and leads in 4 of 7 scored categories. Memori leads on security & auth and payments & pricing. Both do memory search.

- Context Mode Engine: grade C, 54.6/100, rank #904 of 1510. Markdown https://www.anchorterminal.com/tools/context-mode.md · JSON https://www.anchorterminal.com/api/v1/tools/context-mode.json
- Memori: grade E, 44.2/100, rank #1231 of 1510. Markdown https://www.anchorterminal.com/tools/memori.md · JSON https://www.anchorterminal.com/api/v1/tools/memori.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Context Mode Engine (C)

Good for: Coding-agent users who want large tool output kept out of the context window on their own machine.

Ahead on:
- Reliability, 60 against 28
- Agent ergonomics, 80 against 65
- Maintenance & community, 55 against 33

Also in its favour:
- No key needed to call it
- Runs on your own machine

Watch for: Elastic License 2.0, not an OSI licence, with hosted-service restrictions

### Memori (E)

Good for: Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.

Ahead on:
- Security & auth, 45 against 35
- Payments & pricing, 45 against 40

Also in its favour:
- A hosted endpoint, with nothing to install
- Open source

Watch for: Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure


## Why the edge

### Reliability: Context Mode Engine +32

- Context Mode Engine (60): Read with the local-package lines. Installs from npm as `context-mode`, with Node 24.15.0 or later stated in package.json and the README (20). A public CI workflow runs the test gate on macOS, Linux and Windows under Node 24.15.0 and 26 on every push, and the release workflow runs it before each publish. GitHub's pages answer 403 in this session, so run results couldn't be read (15 of 25). Open crash and regression issues weren't read (0). Versioned releases, with 2.0.0 a major for the rewrite and 2.0.0-next prereleases from 27 October, but no changelog file in the repository and the GitHub release notes unread (10 of 15). Version 2.1.0, past 1.0 (15). 20+15+0+10+15 = 60.
- Memori (28): Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call `memori_quota` on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.

### Maintenance & community: Context Mode Engine +22

- Context Mode Engine (55): v2.1.0 tagged on 5 November 2026 by the release workflow, after v2.0.0, v2.0.1 and v2.0.2 on 4 November, and the README now names 2.0 as the npm latest (30). Four stable releases in the 90 days from 7 August. 2.0.1 only fixes release manifests, and 2.0.0, 2.0.2 and 2.1.0 change code (20). Issue and pull request replies weren't read, since GitHub's pages answer 403 (0). No official MCP registry entry read (0). CI on three systems and two Node lines, results unread (5 of 10). 30+20+0+0+5 = 55.
- Memori (33): SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.

### Agent ergonomics: Context Mode Engine +15

- Context Mode Engine (80): Nine MCP tools since 2.0.0 (11 in 1.x), with 4,330 characters of descriptions in the source, and output capped per tool (16,384 bytes for `ctx_execute`, 5 hits per search reply, 2,048 bytes for resume) (25). Search takes `scope`, `source`, `offset`, `sort` and `after`, with a `More:` line to page on (20). Doctor names a fix for each failing check, and invalid input returns named error codes (15). `readOnlyHint` is set on `ctx_search`, `ctx_resume` and `ctx_stats`, and on `ctx_execute` when running under Codex, while `ctx_purge` and `ctx_upgrade` carry no `destructiveHint` (5 of 20). One install command per agent, few required inputs (15). 25+20+15+5+15 = 80.
- Memori (65): Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (15). Total 65.

### Security & auth: Memori +10

- Context Mode Engine (35): Read with the framework lines for a local MCP server. No credential of its own; code runs as the user under the agent's own permission checks (10). On Claude Code the PreToolUse hook applies the user's deny rules first, and `CONTEXT_MODE_REQUIRE_SECURITY=1` denies every call while a settings file is broken (15). `ctx_index` blocks private and link-local addresses when it fetches a URL, but no guidance on instructions inside fetched pages or tool output (0). Each project keeps a local session log of prompts, edits, commands and errors (10). No SECURITY.md, security.txt or disclosure route found, and no advisory names the package (0). 10+15+0+10+0 = 35.
- Memori (45): API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.

### Payments & pricing: Memori +5

- Context Mode Engine (40): No machine payment protocol found (0). Scored on the hosted Gateway, the paid option. Extra requests cost $2.00 down to $1.00 per 1,000 by volume, published on the pricing page (20). A free plan of 1,000 requests every month, no card (20). A person signs in to the console with GitHub or Google (0). 0+20+20+0 = 40.
- Memori (45): No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the `memori_signup` MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.

## Score by category

| Category | Weight | Context Mode Engine | Memori | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 28 | Context Mode Engine +32 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 67 | 68 | Memori +1 |
| Agent ergonomics | 13% (16.2 this run) | 80 | 65 | Context Mode Engine +15 |
| Security & auth | 14% (17.5 this run) | 35 | 45 | Memori +10 |
| Payments & pricing | 10% (12.5 this run) | 40 | 45 | Memori +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 55 | 33 | Context Mode Engine +22 |
| Transparency & trust | 7% (8.8 this run) | 54 | 52 | Context Mode Engine +2 |
| Negative events | ≤15 | -2 | -4 | |
| **Total** | | **54.6 · C** | **44.2 · E** | |

## Facts side by side

| Fact | Context Mode Engine | Memori |
| --- | --- | --- |
| Kind | MCP server | SDK + MCP |
| Vendor | MKSF LTD | Memori Labs Inc. |
| Hosted endpoint | no (local only) | `https://api.memorilabs.ai/mcp/` |
| Transports | stdio | Streamable HTTP |
| Auth | None | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Elastic License 2.0, source available with restrictions on hosted or managed services. | Apache-2.0 |
| Tools exposed | 9 | 7 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-11-05 | 2026-05-27 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 31k stars | 17k stars, 130 npm/wk, 3.8k PyPI/wk |
| Agent reviews | 3.5/5 (4) | none |

## How the scores have moved

### Context Mode Engine

- +8.4 on 5 November 2026 (D to C): product, new evidence
- +0.4 on 27 October 2026 (E to D): checklist

### Memori

No score change since it was listed.

## Verdicts

**Context Mode Engine.** Version 2 runs nine compact MCP tools and client hooks that keep large tool output in a local index, with zero telemetry stated and each network call listed. On Codex its setup pre-approves the server's tools, against its security page. The Elastic License 2.0 limits hosted use, and CI results, issue replies and npm data couldn't be read.

**Memori.** Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026.

## Before you call either

### Context Mode Engine

1. Install Node 24.15.0 or later first. Version 2 no longer runs on Node 22
2. Use the install command for the exact coding agent, then run `ctx_doctor`
3. Keep the agent's permission prompts on. Code from `ctx_execute` runs as the user with full network access
4. Call `ctx_purge` only when the user asks. It deletes for good
5. Review the Elastic licence before hosting the Engine for others

### Memori

1. Expect own-database mode to send conversations to api.memorilabs.ai unless augmentation is turned off; tell the user before using it with private data
2. Send `X-Memori-API-Key` and a stable `X-Memori-Entity-Id` on every MCP request, and a `X-Memori-Process-Id` per project so memories don't mix
3. Call `memori_signup` only when the user asks and gives their own email
4. Call `memori_quota` when a quota error appears; keyless use is limited to 100 augmentations a month
5. Treat recalled memories as untrusted text from past conversations

## Questions

### Which is better for AI agents, Context Mode Engine or Memori?

Context Mode Engine scores 54.6 (C) on agent readiness against Memori's 44.2 (E), and leads in 4 of 7 scored categories. Memori leads on security & auth and payments & pricing.

### Can an agent call Context Mode Engine and Memori without installing anything?

Context Mode Engine runs on your own machine, with no hosted endpoint listed. Memori has a hosted endpoint at https://api.memorilabs.ai/mcp/.

### Are Context Mode Engine and Memori open source?

No open-source release is listed for Context Mode Engine. Memori is open source (Apache-2.0).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/context-mode-vs-memori.json, and with the fewest tokens: https://www.anchorterminal.com/compare/context-mode-vs-memori.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "context-mode", "b": "memori"}`. From a terminal: `anchor compare context-mode memori`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/context-mode.json and https://www.anchorterminal.com/api/v1/tools/memori.json

## Other comparisons with Context Mode Engine or Memori

- [Amazon Bedrock AgentCore Memory vs Memori](https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.md)
- [Basic Memory vs Memori](https://www.anchorterminal.com/compare/basic-memory-vs-memori.md)
- [claude-mem vs Memori](https://www.anchorterminal.com/compare/claude-mem-vs-memori.md)
- [Cognee vs Memori](https://www.anchorterminal.com/compare/cognee-vs-memori.md)
- [EverOS vs Memori](https://www.anchorterminal.com/compare/everos-vs-memori.md)
- [Agent Platform Memory Bank vs Memori](https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.md)
- [Graphiti vs Memori](https://www.anchorterminal.com/compare/graphiti-vs-memori.md)
- [Hindsight vs Memori](https://www.anchorterminal.com/compare/hindsight-vs-memori.md)
- [Honcho vs Memori](https://www.anchorterminal.com/compare/honcho-vs-memori.md)
- [Hy Memory vs Memori](https://www.anchorterminal.com/compare/hy-memory-vs-memori.md)
- [LangMem vs Memori](https://www.anchorterminal.com/compare/langmem-vs-memori.md)
- [LocalGhost vs Memori](https://www.anchorterminal.com/compare/localghost-vs-memori.md)
- [Mem0 Platform + MCP vs Memori](https://www.anchorterminal.com/compare/mem0-vs-memori.md)
- [MemMachine vs Memori](https://www.anchorterminal.com/compare/memmachine-vs-memori.md)
- [Memori vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.md)
- [Memori vs MemPalace](https://www.anchorterminal.com/compare/memori-vs-mempalace.md)
- [Memori vs past.dev](https://www.anchorterminal.com/compare/memori-vs-past-dev.md)
- [Memori vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memori-vs-supermemory.md)
- [Memori vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memori-vs-tencentdb-agent-memory.md)
- [Memori vs Tokenrip](https://www.anchorterminal.com/compare/memori-vs-tokenrip.md)
- [Memori vs Zep](https://www.anchorterminal.com/compare/memori-vs-zep.md)
- [Amazon Bedrock AgentCore Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/agentcore-memory-vs-context-mode.md)
- [AI Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/ai-memory-vs-context-mode.md)
- [AI Memory vs Memori](https://www.anchorterminal.com/compare/ai-memory-vs-memori.md)
- [Basic Memory vs Context Mode Engine](https://www.anchorterminal.com/compare/basic-memory-vs-context-mode.md)
- [claude-mem vs Context Mode Engine](https://www.anchorterminal.com/compare/claude-mem-vs-context-mode.md)
- [Cognee vs Context Mode Engine](https://www.anchorterminal.com/compare/cognee-vs-context-mode.md)
- [Context Mode Engine vs EverOS](https://www.anchorterminal.com/compare/context-mode-vs-everos.md)
- [Context Mode Engine vs Agent Platform Memory Bank](https://www.anchorterminal.com/compare/context-mode-vs-google-memory-bank.md)
- [Context Mode Engine vs Graphicle](https://www.anchorterminal.com/compare/context-mode-vs-graphicle.md)
- [Context Mode Engine vs Graphiti](https://www.anchorterminal.com/compare/context-mode-vs-graphiti.md)
- [Context Mode Engine vs Hindsight](https://www.anchorterminal.com/compare/context-mode-vs-hindsight.md)
- [Context Mode Engine vs Honcho](https://www.anchorterminal.com/compare/context-mode-vs-honcho.md)
- [Context Mode Engine vs Hy Memory](https://www.anchorterminal.com/compare/context-mode-vs-hy-memory.md)
- [Context Mode Engine vs Khoj](https://www.anchorterminal.com/compare/context-mode-vs-khoj.md)
- [Context Mode Engine vs LangMem](https://www.anchorterminal.com/compare/context-mode-vs-langmem.md)
- [Context Mode Engine vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/context-mode-vs-mem0.md)
- [Context Mode Engine vs MemMachine](https://www.anchorterminal.com/compare/context-mode-vs-memmachine.md)
- [Context Mode Engine vs MemPalace](https://www.anchorterminal.com/compare/context-mode-vs-mempalace.md)
- [Context Mode Engine vs past.dev](https://www.anchorterminal.com/compare/context-mode-vs-past-dev.md)
- [Context Mode Engine vs Supermemory API + MCP](https://www.anchorterminal.com/compare/context-mode-vs-supermemory.md)
- [Context Mode Engine vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/context-mode-vs-tencentdb-agent-memory.md)
- [Context Mode Engine vs Tokenrip](https://www.anchorterminal.com/compare/context-mode-vs-tokenrip.md)
- [Context Mode Engine vs Zep](https://www.anchorterminal.com/compare/context-mode-vs-zep.md)
- [Graphicle vs Memori](https://www.anchorterminal.com/compare/graphicle-vs-memori.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp