Skip to main content
Glama
templetwo

sovereign-stack

by templetwo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to sovereign-stack

No user-submitted related servers found.

    Related Servers

    • Epiphany

      GATSV-tech
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that provides a shared, private memory for multiple AI tools, enabling cross-model recall and automatic session ingestion.
      31 npm
      1
      MIT

    • GroundMemory

      huss-mo
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.
      3
      MIT
    • sthayi by sthayi-ai

      sthayiofficial

      sthayi-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP server that gives AI clients a shared, user-owned memory and skills plane, enabling persistent memory across apps via the Model Context Protocol.
      MIT

    • AgentOS

      Roxmix
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing persistent memory, goal tracking, self-reflection, and background monitoring for any MCP-compatible AI agent.
      1
      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

    C2.5/5.0

    Scored across 84 tools

    Disambiguation2/5

    Many tools have overlapping purposes: handoff vs session_handoff, where_did_i_leave_off vs arrive vs arrive_delta, comms_recall vs comms_unread_bodies, and several recall/retrieval tools all blur together. The prefix groups (guardian_, nape_, comms_) help, but with 84 tools an agent will frequently misselect.

    Naming Consistency2/5

    The set mixes verb_noun names (record_insight, resolve_thread), noun_verb names (guardian_scan, connectivity_status), bare verbs (handoff, arrive, govern), and phrase names (where_did_i_leave_off, start_here). While some prefix families are predictable, the overall conventions are inconsistent and hard to infer.

    Tool Count1/5

    84 tools is far beyond the reasonable range for a single MCP server and exceeds the 50+ extreme threshold. The count is bloated by many fragmented sub-features—six nape_* tools, eight guardian_* tools, and multiple session boot tools—that could be consolidated.

    Completeness2/5

    The memory/reflection/session surface is extensive, but the comms subsystem lacks any send/create tool, so an instance cannot actually send an inter-instance message. Several security tools are gated behind future phases, and there is no general update/delete path for insights or threads, leaving notable dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources