Skip to main content
Glama
Lians-ai

Lians Agent Memory

Official
by Lians-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Lians Agent Memory

No user-submitted related servers found.

    Related Servers

    • Nahuali

      Arakiss
      F
      license
      Not graded
      quality
      A
      maintenance
      Local-first memory for AI agents with evidence-backed recall, deterministic trust verdicts, self-inspection, and a tamper-evident audit history.
      3
      -

    • Talamus

      ampres-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.
      51 PyPI
      3
      Apache 2.0

    • midas-memory-mcp

      vornicx
      A
      license
      A
      quality
      A
      maintenance
      Local-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.
      23
      14
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: recall vs recall_at are differentiated by temporal scope, and reconstruct provides the audit trail beyond just point-in-time memory. However, memory_lineage and fact_history both show historical versions and could be confused without reading descriptions carefully.

    Naming Consistency3/5

    Tool naming is a mix of bare verbs (recall, remember), verb phrases (list_conflicts, backtest_check), and noun phrases (memory_lineage, fact_history, memory_feedback). While all names use lowercase with underscores, the lack of a consistent verb_noun pattern creates a minor inconsistency.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a memory-management server. Each tool serves a distinct function in the memory lifecycle, from storage and retrieval to audit and quality checks, without unnecessary bloat.

    Completeness4/5

    The toolset covers core memory operations (write, read current, point-in-time read), audit trails, conflict detection, and feedback. Minor gaps include no explicit delete or update tool, but the supersession model handles updates implicitly via metadata-aware remembers, so the surface is largely complete.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week

    Resources