Skip to main content
Glama
l33tdawg

(S)AGE

by l33tdawg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to (S)AGE

No user-submitted related servers found.

    Related Servers

    • lagrange by MtForme

      lagrangeofficial

      MtForme
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to safely write to and read from persistent memory by validating every write through three independent consensus nodes, storing memories only on 2/3 agreement and quarantining poisoning attempts.
      Apache 2.0
    • Mnemexa MCP by mnemexa

      Mnemexa MCPofficial

      mnemexa
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent, self-optimizing memory for AI agents, enabling them to remember preferences and context across sessions and share knowledge across multiple agents.
      4
      2 npm
      ISC

    • Tideline agent Memory

      ennisaaaaaaaa-stack
      F
      license
      Not graded
      quality
      B
      maintenance
      A long-term memory system built for AI Agents. Agent wakes up already knowing who he is, not querying "who am I?" every session. Every turn calling back accurate memory context. Achieving accurate memory hits while also preventing memory from expanding at scale. No compression, no forgetting.
      39
      -

    • Soul

      choihyunsus
      F
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents persistent memory, handoffs, and shared context across sessions, enabling seamless continuity and multi-agent collaboration.
      49 npm
      67
      -
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 38 tools

    Disambiguation3/5

    The set spans many domains, but the messaging cluster (inbox, history, status, replies, claim, close, reply, handoff) and memory cluster (remember, reflect, turn, recall, list) have overlapping semantics that require careful reading. Descriptions are detailed, but the sheer number of adjacent tools means an agent can easily misselect.

    Naming Consistency4/5

    All tools use snake_case with a consistent sage_ prefix and clear sub-namespaces (message_, gov_, scope_, task_). Verb ordering varies (e.g., sage_message_send vs sage_get_links vs sage_find_agent), which is a minor deviation from a strict pattern.

    Tool Count2/5

    38 tools is excessive for the apparent scope; while each covers a niche operation, many could be consolidated (e.g., scope_get/scope_list, message_status/replies/history). The high count increases cognitive load and the chance of misselection.

    Completeness5/5

    The surface covers memory CRUD (remember/recall/forget/list/link), messaging lifecycle (send/claim/reply/close/handoff), tasks, governance, identity, federation, and node health, leaving no obvious dead ends for the stated purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources