Skip to main content
Glama
context-archive

context-archive

by urcades

Related Servers

Alternatives to context-archive

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to read and search macOS Messages history through a read-only MCP interface.
      -

    TDQS

    C2.4/5.0

    Scored across 14 tools

    Disambiguation2/5

    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 Consistency2/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues