Research pass highlighted governance failures: bad writes, poisoning and privacy boundary leaks become persistent risks.
Tool profile · provisional profile
OpenMemory MCP
Helpful direction: expose memory through a controllable tool surface rather than hiding it inside model behavior.
Provisional fit
67/100
Best for: Personal/workspace memory where users need to see and manage what the agent can remember.
Avoid if: you need a fully governed, citation-complete knowledge architecture without adding policy, evidence capture, and review workflow around the tool.
Caution: A tool surface is only the start. Authority, review, deletion, cross-app boundaries and audit must be explicit.
Model signature: Governance primary · personal scope · Tool
Layer coverage
Where this tool fits.
This is not a completed review. It is a provisional profile from public positioning plus known failure-mode mapping. Hands-on benchmarks, source snapshots, and citation-bound claims are still required before stronger conclusions.
Production
Curation
Storage
Context Assembly
Governance
Review rule: a tool does not get credit for a layer unless it exposes inspectable behavior, not just a marketing claim.
Evidence notes
What the provisional profile has applied so far.
OpenMemory MCP is mapped to governance because MCP makes memory an inspectable capability with explicit tool calls.
Needs hands-on testing for permission boundaries, deletion behavior, source metadata and UX for correction.
Review packet
What a complete review must contain.
This page exposes the intended review structure. The current artifact is a profile, not a completed evidence-backed review.
Canonical source
Strengths
Personal/workspace memory where users need to see and manage what the agent can remember.
Limitations
A tool surface is only the start. Authority, review, deletion, cross-app boundaries and audit must be explicit.
Dimension assessment
Scope, volatility, authority, lifecycle, resource economics, interoperability, and evidence quality must each get a rationale and citations before final scoring.
Open questions
- What can be verified from docs, code, issues, benchmarks, and changelogs?
- Where does the tool fail under stale, contradictory, private, or high-cost knowledge?
- Which claims are vendor claims versus independently observed behavior?
Benchmark critique
No benchmark number is accepted as architectural evidence unless it says which layer it tests and what it misses: lifecycle, scope boundaries, authority, context cost, and governance.
Related systems
Related tools should be connected by evidence-backed edges: competes with, integrates with, implements concept, evaluated by, or has governance gap.
Update history
Provisional profile created. Stale-review detection, source snapshots, and changelog watching are required before this becomes a durable review.