Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want a concrete interop surface for memory syncing across Claude, Cursor, custom agents, and browser-based chat tools.
Who should use it
Who should skip it
Hold off on SMJAI/open-memory-protocol until it graduates from watchlist status with stronger evidence.
About this signal
SMJAI/open-memory-protocol is tracked by RepoRadar as a memory interop protocol in the AI Infrastructure section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. SMJAI/open-memory-protocol leads on novelty (9.0) and open-source/build quality (8.4); its lowest signal is momentum (5.0), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned SMJAI/open-memory-protocol a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The default bridge flow saves and replays cross-tool conversations, so teams should self-host it and set clear retention, access, and API-key boundaries before syncing real work; The sample Claude prompt tells the agent to save memories silently, so operators should tighten consent and policy rules before using it on sensitive conversations.