Skip to main content
Glama
urcades

context-archive

by urcades
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to context-archive

No user-submitted related servers found.

    Related Servers

    • Archive MCP Server

      Surajp1602
      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.
      -

    • message-container

      B-HS
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to read and search macOS Messages history through a read-only MCP interface.
      -

    • sqlite-mcp-local

      Ajaytechgenius
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only querying of a local SQLite database via MCP, with tools to list tables, retrieve schema, and execute SELECT/WITH/EXPLAIN queries.
      -

    • pywel

      RolandSaint
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query a local, offline Crimson Desert knowledge base through stdio MCP, providing versioned entity/claim lookups, bounded search, codebook decoding, and typed responses with provenance context.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources