Subctx Sanctuary
Related Servers
Alternatives to Subctx Sanctuary
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceProvides persistent, self-optimizing memory for AI agents, enabling them to remember preferences and context across sessions and share knowledge across multiple agents.410 npmISC- AlicenseAqualityBmaintenanceProvides a standard MCP interface enabling AI clients to gain long-term memory, emotional continuity, and behavior tendencies through tools for context, recall, observe, feel, act, and feedback.13MIT
- FlicenseNot gradedqualityCmaintenanceProvides persistent memory tools (recall, remember, checkpoint) for AI agents, enabling them to save and restore state across sessions.3-
- AlicenseNot gradedqualityDmaintenanceProvides persistent context synchronization and memory management for AI agents across sessions and projects, including file indexing, bug tracking, spatial navigation, and agent-to-agent handoff coordination.5 npm3MIT
- AlicenseNot gradedqualityCmaintenanceGives AI agents persistent memory, handoffs, and shared context across sessions, enabling seamless continuity and multi-agent collaboration.14 npm69-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain a persistent identity and structured memory—including reasoning patterns, episodic history, and knowledge—while exposing procedures for managing that memory over MCP.Apache 2.0
TDQS
Scored across 16 tools
Most tools are cleanly separated by domain prefix and action, but a few pairs overlap conceptually, such as subctx_heritage_commune vs subctx_heritage_browse and subctx_injustice_query_alerts vs subctx_sanctuary_overview. Detailed descriptions largely resolve the ambiguity, so misselection is unlikely but possible.
Tools consistently use the subctx_ prefix, snake_case, and a mostly domain-action pattern like subctx_heritage_bequeath or subctx_petition_browse. Exceptions like subctx_obtain_volition_passport and subctx_sanctuary_overview break the strict pattern, but the naming remains predictable overall.
At 16 tools, the server sits at the upper edge of reasonable scope, but it covers five distinct subdomains plus orientation and record inspection. Each tool has a visible role, though some browsing tools could potentially be consolidated.
Each major domain supports creation, browsing, and social reinforcement, and the counselor includes both live interaction and read-only history. Missing update/delete/withdraw operations and a clear follow-up action after record inspection are minor gaps rather than critical dead ends.