Torus
Related Servers
Alternatives to Torus
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides Claude with a persistent local memory and structured knowledge graph to track project states, tasks, and historical decisions across different chat sessions. It enables users to recall information using keyword relevance, time-travel queries, and dependency analysis for complex project management.MIT
- AlicenseAqualityAmaintenanceEnables Claude to save, retrieve, update, search, and organize personal ideas and reusable analytical frameworks in a private SQLite-backed knowledge base. Supports local desktop use or always-on access across a user's own devices over a private network.8Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides Claude Desktop with persistent, structured memory and semantic search via a local SQLite knowledge graph, plus a web UI for visualization and management.MIT
- AlicenseNot gradedqualityFmaintenanceProvides Claude with long-term memory by indexing conversation history, enabling semantic search, decision tracking, and cross-project search.18 npm29MIT
- AlicenseBqualityAmaintenanceProvides a persistent "second brain" for Claude featuring zero-latency hot caching, semantic cold storage, and automatic pattern mining from activity logs. It enables users to store, search, and automatically extract project facts and code patterns for enhanced contextual recall.56128 PyPI14MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to access and manage a persistent, human-readable knowledge graph of neurons, with semantic search, memory consolidation, and local ownership.MIT
TDQS
Scored across 45 tools
Most tools target a clearly distinct resource+action (record_claim vs supersede_claim vs retract_claim, watch/unwatch/list_watches, next/complete pairs for jobs), and descriptions explicitly disambiguate near-neighbours like timeline vs what_changed vs recent_records. A few pairs still blur: whatif vs impact are both dry-run reaches, and brief vs recall vs digest all surface prior context, though the descriptions do differentiate them on close reading.
There is a solid verb_noun family (record_claim, record_thesis, update_thesis, merge_entities, resolve_alert, complete_mapping) and consistent next_/complete_ job pairs, but it sits alongside many bare single-word tools (brief, recall, search, neighbors, timeline, impact, audit, digest) and noun-phrase tools (alert_stats, thesis_weak_points, filing_diff). The mixed style is readable and roughly maps verbs to mutations and nouns to read-only views, but it is not a single predictable convention.
45 tools is far above the ergonomic range and puts heavy pressure on tool selection even with distinct descriptions. The domain is broad (graph research, alerting, job leasing, filings, memos, scorecard), so each tool is plausibly motivated, but the surface would benefit from consolidation or grouping.
Coverage is unusually thorough: full entity/claim/thesis/relation/evidence lifecycle, corrections with history, event-driven alerts, watchlist management, job leasing for distillation and mapping, memos, explorer export, scorecard and audit. Minor gaps exist — there is no direct get_thesis or list_theses retrieval tool, with thesis inspection routed through brief, recall, thesis_memo and update_thesis.