Skip to main content
Glama
n0zer0d4y

Chronos Protocol

by n0zer0d4y
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Chronos Protocol

No user-submitted related servers found.

    Related Servers

    • engram

      coinstax
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent project memory for AI coding agents, enabling context retention across sessions via event logging, briefing generation, and querying.
      MIT
    • Hebbrix MCP Server by Hebbrix

      Hebbrix MCP Serverofficial

      Hebbrix
      A
      license
      A
      quality
      A
      maintenance
      Provides long-term memory and a temporal knowledge graph for AI agents, enabling persistent memory and reasoning across sessions.
      33
      110 PyPI
      2
      MIT

    • ProactiveAgent

      ConradLu2740
      A
      license
      A
      quality
      A
      maintenance
      Provides shared long-term memory and proactive suggestions across AI coding agents, enabling persistent user preferences and behavior rules that are remembered and applied across different tools. Includes memory capture, recall, extraction, and suggestion tools with a local-first and privacy-focused design.
      20
      1
      MIT

    • BuildAutomata Memory MCP

      brucepro
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.
      14
      -
    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

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools like 'check_time_reminders', 'create_time_reminder', 'get_current_time', and 'convert_time' each handle specific time-related tasks, while 'start_activity_log', 'end_activity_log', 'get_activity_logs', 'update_activity_log', and 'get_elapsed_time' form a complete activity logging lifecycle. There is no overlap in functionality that could cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case throughout. Examples include 'check_time_reminders', 'convert_time', 'create_time_reminder', 'start_activity_log', and 'update_activity_log'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.

    Tool Count5/5

    With 9 tools, the count is well-scoped for the server's purpose of time management and activity logging. Each tool earns its place by covering distinct aspects such as time retrieval, conversion, reminders, and activity tracking. This number is neither too thin nor too heavy, fitting typical expectations for a focused domain.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for both time management and activity logging domains. For time, it includes creation, checking, conversion, and retrieval. For activities, it supports starting, ending, updating, retrieving, and calculating elapsed time. There are no obvious gaps or dead ends that would cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources