Skip to main content
Glama
tinytelly

Time MCP Server

by tinytelly

Related Servers

Alternatives to Time MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      Not graded
      maintenance
      Provides AI assistants with real-time date, time, and timezone information, enabling them to access current temporal data, format dates, calculate day of week, and work with different timezones.
      4
      7 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides current time information and timezone conversion capabilities using IANA timezone names and automatic system detection. It enables LLMs to fetch current times across different regions and convert specific times between timezones.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides time and date functionality with support for multiple formats and timezones, enabling users to get current time/date, format timestamps, and retrieve comprehensive datetime information.
      125 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to get current time information for any timezone worldwide, including available regions, cities, and ISO 8601 formatted timestamps with timezone offsets.
      8
      -
    • A
      license
      B
      quality
      D
      maintenance
      Gives large language models time awareness capabilities through various time-related functions including current time retrieval, timezone conversion, and relative time calculations.
      6
      2,318 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides LLMs with current date and time information across any timezone, with configurable defaults and support for IANA timezone identifiers.
      1
      17 npm
      3
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 2 tools

    Disambiguation2/5

    The two tools have overlapping purposes: both retrieve time-related information, with 'get_current_time' focusing on basic date/time and 'get_time_info' adding details like timezone and day of week. This creates ambiguity as an agent might struggle to choose between them for general time queries, since their boundaries are unclear and they could be confused for similar tasks.

    Naming Consistency5/5

    The tool names follow a consistent verb_noun pattern with 'get_' prefix and snake_case formatting throughout. Both tools start with 'get_' followed by descriptive nouns ('current_time', 'time_info'), making the naming predictable and readable without any deviations or mixed conventions.

    Tool Count2/5

    With only 2 tools, the server feels too thin for a time-related domain, as it lacks basic operations like time conversion, timezone handling, or scheduling functions. This minimal set limits functionality and suggests an incomplete scope, making it borderline inadequate for typical time management tasks.

    Completeness2/5

    The tool surface is significantly incomplete for a time server domain. It only provides retrieval functions without essential operations such as time conversion between zones, date arithmetic, scheduling, or alarm setting. These gaps will likely cause agent failures when trying to perform common time-related workflows beyond simple queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues