Memori vs MemPalace

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.

MemPalace 77

Read with the local-software lines, as software the owner runs. PyPI package mempalace and a multi-arch ghcr.io image, with Python 3.10 or later and Linux, macOS and Windows stated (20). The Tests workflow runs pytest on Linux with Python 3.10, 3.11 and 3.13 and on Windows and macOS, and its push runs on develop on 20 and 25 October 2026 passed (25). 387 open issues against 1,311 workflow runs on develop and 30 listed contributors; the seven newest open issues each had a reply, and we did not sort the backlog for crash reports, so the early macOS ARM64 segfault (#74) and later ones were not counted (12 of 25). Keep a Changelog with upgrade notes on each release, but minor versions remove modules and Python versions, as the 3.12.0 notes (dated 31 October, not yet tagged on 1 November) drop mempalace.dedup, onboarding and Python 3.9 (10 of 15). Version 3.11.0, while pyproject.toml still classifies the package as Development Status 4 - Beta (10 of 15).

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.

MemPalace 74

v3.11.0 was released on 14 October 2026, 18 days before this check, and no newer tag exists on 1 November although the changelog dates 3.12.0 on 31 October (30). Six releases in the 90 days to 1 November, 3.7.0 on 11 August, 3.7.1, 3.8.0, 3.9.0, 3.10.0 and 3.11.0 (20). Per the 30 October check, 387 open issues and about 478 open pull requests; the seven newest open issues each had one reply, and Igor Lins e Silva has 1,444 commits and code ownership of every path. The clone shows merged fixes on develop on 30 and 31 October (15 of 25). Not in the official MCP registry under a MemPalace namespace; the only match is a third party's io.github.holetron/hindsight-mempalace (0 of 15). Dependabot updates on 23 and 30 October, a version guard workflow, chromadb pinned below 2 and CI passing per the 30 October check (9 of 10).

Memori 68

No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid source and signal pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.

MemPalace 85

All 47 tools in schemas.py carry a JSON Schema input_schema, and the remote server guide says arguments are checked against it before any handler runs (25). No llms.txt on mempalaceofficial.com (404), but the docs are Markdown in website/ in the repository (10). Descriptions state purpose and sometimes when not to use a tool, as mempalace_search says it is not for the current conversation and mempalace_checkpoint says to use it in place of several calls, while many are one line such as "List all wings with drawer counts" (12 of 20). Search has maxLength 250, limit 1 to 100 and enums for candidate_strategy and query_task, but direction on mempalace_kg_query is a free string and metadata on mempalace_patch_submit is a free object (11 of 15). The tool reference documents return shapes, error codes -32003, -32005 and -32602, and action_required fields, with few worked examples (12 of 15). Semantic versioning, dated releases and a public changelog (15).

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.

MemPalace 60

Read with the self-hosted rule. No payment protocol (0). Free under MIT with no hosted option and nothing to buy, so 20, 20 and 20 on the last three lines. LLM reranking and managed backends are optional and billed by their own providers.

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.

MemPalace 75

47 tools in the default server (5), with 10 added back for mempalace-light-mcp, which puts the same operations behind 3 tools, and --read-only, which hides the write tools (15 of 25). Search takes limit, wing, room, source file, since, before and a distance cutoff, mempalace_list_drawers pages with limit and offset, batch reads take 1 to 500 IDs, and long mine output is trimmed with output_truncated (18 of 20). Errors are JSON-RPC codes with a hint, refusals name the variable or step that clears them, and a failed mine lists its failed files (17 of 20). readOnlyHint on read tools but no destructiveHint, deletes are irreversible, mempalace_delete_by_source dry-runs by default, mempalace_add_drawer checks for duplicates, drawer IDs are deterministic and a mutating call that failed mid-flight through the proxy is never replayed (13 of 20). Only query is required for search and the default backend needs no configuration; the interfaces are Python and a Rust native CLI, not SDKs for a service (12 of 15).

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.

MemPalace 53

Local MCP reading. Over stdio nothing needs a credential and the README says nothing leaves the machine unless you opt in. The HTTP hub needs a bearer token off loopback, kept 0600 and passed by environment, but it is one token with full access, no scopes and no per-user keys (15 of 30). A server-wide --read-only mode, dry run by default on bulk delete and a 500-ID cap, but no confirmation step on the delete tools and an advisory showed gaps in read-only mode until 3.7.0 (14 of 20). Search returns verbatim transcripts and mined files, and we found no prompt-injection guidance in the docs, the skills or the code; the query sanitiser deals with prompts pasted into queries, not injected content (2 of 15). A write log at ~/.mempalace/wal/write_log.jsonl records each write and its outcome with content redacted, and /statusz reports request counters and recent clients (11 of 15). SECURITY.md with private reporting and a 48-hour acknowledgement target, one published advisory with credit, Dependabot, and Chroma server CVEs documented. No security.txt, bug bounty, CodeQL workflow or audit (11 of 20).