Skip to main content
Glama
IBM

chuk-mcp-time

by IBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TIME_SERVER_MIN_SOURCESNoMinimum number of sources required (1 to 10)3
TIME_SERVER_NTP_SERVERSNoNTP Servers (comma-separated)time.cloudflare.com,time.google.com,time.apple.com
TIME_SERVER_NTP_TIMEOUTNoNTP timeout in seconds (0.5 to 10.0)2.0
TIME_SERVER_MAX_DISAGREEMENT_MSNoMaximum disagreement before warning in milliseconds (10.0 to 5000.0)250.0
TIME_SERVER_FAST_MODE_SERVER_COUNTNoNumber of servers to query in fast mode (2 to 10)4
TIME_SERVER_MAX_OUTLIER_DEVIATION_MSNoMaximum outlier deviation in milliseconds (100.0 to 60000.0)5000.0

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_time_utcA

Get current UTC time with high accuracy using NTP consensus.

Queries multiple NTP servers, removes outliers, and computes a consensus time
that is independent of the system clock. Returns detailed information about
all sources, consensus method, and estimated error.

By default, the returned timestamp is compensated for the time it took to
query NTP servers and compute consensus. This means the timestamp represents
the time when the response is returned, not when NTP servers were queried.

Args:
    mode: Accuracy mode - "fast" uses 3-4 servers, "accurate" uses 7 servers
    compensate_latency: If True, add query duration to timestamp (default: True)

Returns:
    TimeResponse with consensus time and metadata
get_time_for_timezoneA

Get current time for a specific timezone with high accuracy.

Queries multiple NTP servers for accurate UTC time, then converts to the
requested timezone. Includes all consensus metadata and source details.

Args:
    timezone_name: IANA timezone name (e.g., "America/New_York")
    mode: Accuracy mode - "fast" or "accurate"
    compensate_latency: If True, add query duration to timestamp (default: True)

Returns:
    TimezoneResponse with time in specified timezone
compare_system_clockA

Compare system clock against trusted NTP time sources.

Useful for detecting system clock drift or misconfiguration. Queries NTP
servers and reports the difference between system time and consensus time.

Args:
    mode: Accuracy mode - "fast" or "accurate"

Returns:
    ClockComparisonResponse with comparison data
get_local_timeA

Get current time for a specific IANA timezone with high accuracy.

Uses NTP consensus for accurate UTC time, then converts to the requested
timezone using IANA tzdata. This provides authoritative local time independent
of system clock accuracy.

Args:
    timezone: IANA timezone identifier (e.g., "America/New_York", "Europe/London")
    mode: Accuracy mode - "fast" or "accurate"
    compensate_latency: If True, add query duration to timestamp (default: True)

Returns:
    LocalTimeResponse with local time and timezone metadata
convert_timeA

Convert a datetime from one timezone to another using IANA rules.

Performs timezone conversion independent of system clock. Uses IANA tzdata
to handle all DST transitions, historical changes, and political boundaries.

Args:
    datetime_str: ISO 8601 datetime string (naive, will be interpreted in from_timezone)
    from_timezone: Source IANA timezone identifier
    to_timezone: Target IANA timezone identifier

Returns:
    TimezoneConversionResponse with conversion details and explanation
list_timezonesA

List available IANA timezones with optional filtering.

Returns all valid IANA timezone identifiers. Helps discover correct timezone
names and prevents hallucination of invalid timezones.

Args:
    country_code: Optional ISO 3166 country code filter (e.g., "US", "GB", "FR")
    search: Optional substring search filter (case-insensitive)

Returns:
    ListTimezonesResponse with list of timezones and metadata
get_timezone_infoA

Get detailed information about a timezone including upcoming transitions.

Provides comprehensive timezone metadata including current offset, DST status,
and upcoming transitions (e.g., DST changes). Useful for planning and
understanding timezone behavior.

Args:
    timezone: IANA timezone identifier
    mode: Accuracy mode for getting current time - "fast" or "accurate"

Returns:
    TimezoneDetailResponse with current info and transition schedule

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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 7 tools

Disambiguation3/5

Most tools are distinct, but get_local_time and get_time_for_timezone have overlapping purposes: both return current time for a timezone with the same parameters. This could confuse an agent about which to use.

Naming Consistency5/5

All tool names use consistent snake_case and follow a verb_noun pattern (e.g., get_local_time, convert_time, list_timezones). No mixed conventions.

Tool Count5/5

7 tools is a well-scoped set for a time utility server, covering essential operations without unnecessary bloat.

Completeness4/5

Covers core time functions: UTC time, local time, timezone conversion, listing timezones, and system clock comparison. Minor redundancy (two local time tools) but no obvious gaps.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources