Item detail
github.com

Uranid/mnem

RepoRadar surfaced Uranid/mnem — a agent memory — into the Agents and Automation section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 10.0 out of 10.

Score8.5
Popularity1.0
Risknone
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum6.0
Maturity6.6
Open-source/build8.4
Evidence8.0
Workflow potential10.0
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for teams that want a durable memory layer they can diff, branch, and ship with the codebase instead of handing long-horizon agent state to a hosted black box.

Who should use it

Teams that want project memory under version controlDevelopers wiring one memory layer into Claude Code, Cursor, Gemini CLI, or other MCP hostsBuilders who need offline retrieval instead of a hosted memory productEngineers comparing graph-aware memory systems against simpler vector stores

Who should skip it

Skip Uranid/mnem if the source link, documentation, or setup requirements do not align with your current workflow or stack.

About this signal

Uranid/mnem is tracked by RepoRadar as a agent memory in the Agents and Automation section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, Uranid/mnem is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on momentum (6.0) — a profile worth weighing against your own priorities. 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 Uranid/mnem a composite score of 8.5 out of 10, placing it in the Gold 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 'none' 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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
memorymcpgraphragofflinerustapache-2.0