Skip to main content
Glama

Related Servers

Alternatives to Facthouse

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A persistent, searchable memory layer for AI assistants, exposed as an MCP server. It supports CRUD, namespaces, hybrid ranked search, relationships, chat-context assembly, import/export, and optional LLM-powered auto-extraction.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open-source MCP memory server providing persistent, cross-platform context for AI tools via a knowledge graph with encrypted storage.
      7 npm
      13
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that provides a personal semantic memory layer for AI tools. It enables storing, searching, and managing memories using hybrid vector and keyword search, allowing AI assistants to recall information by meaning.
      MIT

    TDQS

    A4.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    The recall trio (search_knowledge, get_entity, get_context) genuinely overlaps — all three can answer 'what do you know about X' — but the descriptions draw explicit boundaries (fast fact vs. subject dossier vs. relationship traversal) and cross-reference each other. capture_fact vs. log_event is cleanly separated as meaning vs. raw utterance, and the utility tools (get_stats, get_schemas, consolidate, get_session_context) are unambiguous. Only a careless agent would misselect, but the overlap is real enough to keep this below 5.

    Naming Consistency4/5

    Consistent snake_case with a strong verb_noun pattern throughout: search_knowledge, get_entity, get_context, get_schemas, get_stats, log_event, get_events, capture_fact, get_session_context. The single bare imperative 'consolidate' is the one deviation. Easily predictable for an agent.

    Tool Count5/5

    Ten tools is well-scoped for a persistent-memory store: capture, retrieve (three granularities), inspect, log, and batch-consolidate each earn their place. No redundant aliases and nothing obviously missing from the count itself.

    Completeness3/5

    Read and write paths are thorough — capture, search, entity/topic traversal, raw event log, stats, schema listing, and consolidation for dedup/contradiction. However, there is no update or delete/forget operation for a stored fact or entity, which is a notable gap for a memory store where users will ask to correct or remove knowledge; the server expects reconciliation to handle it implicitly. Coverage of the lifecycle is therefore write-heavy but not closable by the agent.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled