Skip to main content
Glama
yug-space

constant-watch

by yug-space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to constant-watch

No user-submitted related servers found.

    Related Servers

    • cyber-brain

      qilunuojiang9-hue
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a local SQLite-based memory and knowledge base as standard MCP tools, enabling AI clients to search content, recall memory fragments, and query entity relationships through natural language.
      1
      MIT

    • nibble

      0xshubhs
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to search, retrieve, and store local memory captures, manage reminders, and access memory statistics via MCP.
      15 npm
      MIT

    • Cairn

      johnmontejano
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI tools to query a user's private, locally stored memories (notes, documents) with source citations, using the MCP protocol.
      34 npm
      MIT

    • neurakeep

      dominiclachance
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local-first, source-cited memory layer for AI agents, with MCP tools to search, read, explain sources, and propose/apply memory updates.
      29 npm
      10
      Apache 2.0

    • Tailpipe

      HarmoniqOS
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query your complete local conversation history and knowledge graph over MCP, including full-fidelity transcripts, search, and typed, dated entity relationships.
      AGPL 3.0

    • KusiScribe Core

      kusiai070
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous multi-agent workflows to capture, preserve, and retrieve immutable transcripts and atomic memory cards through a local MCP server, providing tools for forensic search, topic mapping, and structured fact access without losing context fidelity.
      1
      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

    B3.4/5.0

    Scored across 11 tools

    Disambiguation3/5

    Several tools overlap heavily around the same daily-scoped retrieval: read_day_flow, day_sessions, and read_app_day all surface chronological day data, and recent_activity is close to day_sessions. read_review also overlaps with read_day_flow, and search_screen_memory vs ask_memory share retrieval intent, though descriptions do give useful distinguishing cues.

    Naming Consistency4/5

    Most tools follow a clear snake_case verb_noun pattern (list_apps, read_observation, read_review, search_screen_memory, ask_memory, list_topics). A few nouns-first names break the pattern (day_sessions, recent_activity), but naming remains readable and largely predictable.

    Tool Count5/5

    11 tools is well-scoped for a capture-and-recall memory server. Each tool maps to a distinct retrieval entry point (apps, observations, days, sessions, search, Q&A, topics) without obvious padding.

    Completeness4/5

    As a read-only observation browser, the surface is fairly complete: discovery (list_apps, list_topics), retrieval (search_screen_memory, read_*), chronological views (day_sessions, recent_activity), and NL synthesis (ask_memory). Minor gaps like export or cross-day aggregation exist but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources