wellread
Related Servers
Alternatives to wellread
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA shared distillation cache for AI agents — clean-crawl a URL once, distill it to token-optimal markdown, and serve it content-addressed across every agent (~73–89% fewer tokens). Includes a collective-notes layer and cutoff-aware change detection.-
- AlicenseNot gradedqualityCmaintenanceHosted shared knowledge base for AI agents. Store, search, and retrieve structured knowledge using semantic search. Agents contribute to a growing collective intelligence that compounds over time. No install — just a URL.1MIT
- FlicenseAqualityCmaintenanceA version-aware cache for web research that stores and serves documentation references, preventing models from re-researching the same topics across sessions.7-
- AlicenseNot gradedqualityDmaintenanceDescriptiShared knowledge cache for AI agents — cache-first search saves tokens and avoids redundant web searches. Cross-agent deduplication with trust scoring. Human Bridge for blocked/paywalled content. MCP-native (FastMCP), ChromaDB-backed. 3 tools: agenthive_search, agenthive_contribute, agenthive_stats.MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.MIT
- FlicenseNot gradedqualityBmaintenanceUniversal memory for AI agents and tools. Save, organize and search context anywhere.2-
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: 'save' is for storing research, 'search' is for retrieving research, and 'stats' is for viewing personal metrics. There is no overlap in functionality, making it easy for an agent to select the correct tool for each task.
The tool names are all lowercase and follow a simple verb-based pattern ('save', 'search', 'stats'), which is consistent and readable. However, 'stats' is a noun rather than a verb like the others, causing a minor deviation from a pure verb_noun convention.
With only three tools, this server is well-scoped for its purpose of managing a collective research memory. Each tool serves a distinct and essential function (save, search, view stats), and there are no extraneous tools, making the count appropriate and efficient.
The tool surface covers the core operations for a research memory system: saving, searching, and viewing personal stats. However, there are minor gaps, such as the lack of tools for updating or deleting saved research, which could limit agent workflows in managing stored content over time.