Skip to main content
Glama
bosprimigenious

continuum

by bosprimigenious
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to continuum

No user-submitted related servers found.

    Related Servers

    • chist

      hiropon164
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for unified full-text search across chat histories from Claude Code, Codex, Cursor CLI, and Antigravity CLI, using SQLite FTS5. Provides read-only tools to search sessions, list conversations, and retrieve session details.
      MIT

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

    • retrace-mcp

      calvingunther66
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for searching your local Retrace screen-history database, with tools for full-text search, segment listing, frame details, app usage, and tags.
      6
      MIT

    • signal-mcp

      NathanDai5287
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to Signal Desktop message history, enabling listing conversations, retrieving messages, and searching messages through MCP tools.
      MIT
    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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing sources, listing sessions, searching text, and reading full events. The overlap between search and read is well-defined, with search for discovery and read for retrieval.

    Naming Consistency5/5

    All tools follow a consistent history_ verb_noun pattern (sources, list, search, read). The naming is predictable and immediately conveys the action and resource.

    Tool Count5/5

    With only 4 tools, the server is well-scoped for a read-only history/event domain. Each tool earns its place, covering the essential operations without unnecessary bloat.

    Completeness4/5

    The surface covers listing, searching, and reading, which are the core operations for a history server. Minor gaps exist, such as no rich filtering for sessions, but agents can work around these limitations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources