Skip to content
Memgar logo

Memgar

Inspects LLM agent memory writes and retrievals with pattern, similarity and provenance checks to block poisoned entries.

Actively maintained

Memgar: data, price, alternatives
At a glancechecked Oct 31, 2026

16 installs/mo

Emerging

For
developers of LLM agents with persistent memory, guarding against memory poisoning
Activity
Actively maintainedrelease 5 months ago · site updated 13 days ago
How it runs
SDK
Used for
  • screen memory writes for injected instructions before storage
  • detect tampered memory entries after they were stored
  • check retrieved chunks and tool results before the model sees them
Worth knowingcomputed from what we read · each with its source
  • Launched on Product Hunt on Jun 1, 2026Product Hunt ↗
Your datawhat they publish, each line with its page · read Oct 22, 2026

    These are Memgar's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.

    Most used in Developer toolsby use, among tools still maintained — this tool shares no tags yet

    Figure and bar: visits/mo, estimate · year: online since

    Compare Memgar with

    Pick up to two.

    All 10 alternatives to Memgar →

    All Developer tools tools →

    Not it? Say what you need

    beta

    Three tools from the Atlas for the job you describe, each with what fits and what does not.

    From people who use itnot part of the reading

    No notes yet. What do you use Memgar for?

    Sign in to leave a note
    Questions this page answers
    • What is Memgar?

      Inspects LLM agent memory writes and retrievals with pattern, similarity and provenance checks to block poisoned entries. It is listed in the Atlas under Developer tools.

    • Who is Memgar for?

      developers of LLM agents with persistent memory, guarding against memory poisoning

    • Do people use Memgar?

      Emerging: 16 installs/mo (pypi).

    • Is Memgar still maintained?

      Actively maintained: release 5 months ago · site updated 13 days ago.

    How we read a tool

    No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

    • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
    • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
    • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
    • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

    How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

    How we read every tool → · By INITE Atlas Desk