context-archive
Related Servers
Alternatives to context-archive
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to inspect and synchronize local macOS QQ data snapshots, with read-only access to contacts, conversations, messages, search, changes, exports, full tables/datasets, media assets, and favorites via MCP tools.MIT
- AlicenseAqualityBmaintenanceEnables local, offline inspection of computer activity by collecting visible process, connection, and automatic-launch metadata and letting MCP clients explain rule matches and process context. It is read-only toward processes and system settings and offers review suggestions without making changes.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP client to search and read macOS Messages history from a local chat database, including conversations, unread messages, and Contacts-based names. It is read-only, runs over stdio, and cannot send, edit, or delete messages.674 npmMIT
- AlicenseAqualityBmaintenanceProvides read-only MCP tools to inspect imported history sources, list sessions, search literal text, and read paginated event history from a local SQLite index.42MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI clients to read and search macOS Messages history through a read-only MCP interface.-
TDQS
Scored across 14 tools
Many tools share the exact same description prefix 'bounded read-only archive retrieval,' making it difficult to distinguish e.g. search from query, or timeline from episodes from project_timeline. A few tools are clearer, but the set has notable overlapping retrieval purposes.
Naming is inconsistent: single-word nouns like 'status' and 'sources' sit alongside verb-prefixed names like 'get_record' and 'decode_blob,' compound nouns like 'app_usage_summary,' and multiword names like 'project_timeline.' No consistent verb_noun or noun_noun convention is maintained.
Fourteen tools is within a reasonable range for an archive-retrieval server. The count feels slightly padded because several tools may overlap, but it is not excessive or clearly under-scoped.
The tool set covers core retrieval operations, schema introspection, blob decoding, and timeline/summary views, which is plausible for a read-only archive. However, there are gaps such as no obvious listing/enumeration of available sources or archives, and the relationship between query, search, and get_record is unclear enough to create potential dead ends.