Loading connector details…
Loading connector details…
Choose a unique username to continue using AgentHotspot
by andybrandt • Analytics & Monitoring
Provides local and NTP-sourced UTC time tools for MCP clients so LLM agents can obtain accurate timestamps and timezone information.
The user's current local time and timezone to make time-aware decisions or calculate durations since previous interactions.
Authoritative UTC time fetched via NTP for timestamping, synchronization, or scheduling tasks.
A simple MCP-compatible endpoint they can run locally or use a hosted endpoint to supply accurate time to Claude-like LLM clients.
MCP Simple Timeserver is a lightweight MCP server that exposes two tools: get_local_time (returns the user's local time and timezone) and get_utc (returns current UTC time from an NTP server). It enables agents like Claude, which lack native awareness of the current time, to perform time-aware reasoning, compute elapsed durations, and schedule actions. The server can be run locally as a Python module or deployed as a standalone web server, and a public hosted endpoint is provided by the author.
Returns the current local time and timezone information from your local machine. This helps you understand what time it is for the user you're assisting.
Returns accurate UTC time from an NTP server. This provides a universal time reference regardless of local timezone. :param server: NTP server address (default: pool.ntp.org)
Returns current time, optionally localized to a specific location or timezone, with optional conversion to additional calendar systems. LOCATION PARAMETERS (use one, priority: timezone > city > country): :param city: City name (PRIMARY USE CASE). Examples: "Warsaw", "Tokyo", "New York" Resolves city to timezone automatically. Best for most queries. :param country: Country name or code. Examples: "Poland", "JP", "United States" Falls back to capital/major city timezone. Use when city is unknown. :param timezone: Direct IANA timezone or UTC offset. Examples: "Europe/Warsaw", "+05:30" Escape hatch for precise control. Use when you know the exact timezone. When a location is provided, the response includes: - Local time at that location - Timezone name and abbreviation (e.g., "Europe/Warsaw (CET)") - UTC offset (e.g., "+01:00") - DST status (Yes/No) - UTC time for reference When NO location is provided, returns UTC time only (original behavior). CALENDAR PARAMETER: :param calendar: Comma-separated list of additional calendars/formats. Valid values (case-insensitive): - "unix" - Unix timestamp (seconds since 1970-01-01) - "isodate" - ISO 8601 week date (YYYY-Www-D) - "hijri" - Islamic/Hijri lunar calendar - "japanese" - Japanese Era calendar (English and Kanji) - "persian" - Persian/Jalali calendar (English and Farsi) - "hebrew" - Hebrew/Jewish calendar (English and Hebrew script) Calendars are calculated for the LOCAL time when location is specified. EXAMPLES: - get_current_time(city="Warsaw") - Time in Warsaw with timezone info - get_current_time(city="Tokyo", calendar="japanese") - Tokyo time with Japanese calendar - get_current_time(timezone="+05:30") - Time at UTC+5:30 offset - get_current_time() - UTC time only (no location) Uses accurate time from NTP server when available. Invalid locations fall back to UTC with a helpful message.
Calculate the duration/distance between two dates or datetimes. Use this tool for countdowns, elapsed time calculations, or scheduling queries. :param from_date: Start date in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS) or "now". Examples: "2025-01-15", "2025-01-15T09:30:00", "now" :param to_date: End date in ISO 8601 format or "now". Examples: "2025-12-31", "2025-06-01T17:00:00", "now" :param unit: Output format for the distance. Options: - "auto" (default) - Human-readable breakdown (e.g., "15 days, 3 hours, 45 minutes") - "days" - Decimal days (e.g., "15.50 days") - "weeks" - Decimal weeks (e.g., "2.21 weeks") - "hours" - Decimal hours (e.g., "372.00 hours") - "minutes" - Decimal minutes (e.g., "22320.00 minutes") - "seconds" - Total seconds (e.g., "1339200 seconds") LOCATION PARAMETERS (optional, same as get_current_time): :param city: City name for timezone context. Examples: "Warsaw", "Tokyo", "New York" :param country: Country name or code. Examples: "Poland", "JP" :param timezone: Direct IANA timezone or UTC offset. Examples: "Europe/Warsaw", "+05:30" Location affects how dates without explicit timezone are interpreted. Priority: timezone > city > country. If none provided, UTC is used. OUTPUT FORMAT: - Distance: The calculated duration - Human readable: Simplified summary (when unit="auto") - Direction: "future" if to_date > from_date, "past" if to_date < from_date - From/To: The parsed datetime values - UTC Reference: Both times converted to UTC BUSINESS DAYS MODE (optional): :param business_days: Count only business days (Mon-Fri), excluding weekends. Default: False. When True, returns business day count instead of elapsed-time duration. Time-of-day is ignored; dates are counted as full days (inclusive endpoints). The `unit` parameter is ignored in this mode. :param exclude_holidays: Also exclude public holidays. Default: False. Only effective when business_days=True. Requires country or city parameter to determine which holidays to exclude. If country cannot be determined, proceeds with weekend-only exclusion. Example: "How many business days until project deadline?" from_date="now", to_date="2026-03-15", business_days=True, country="Poland" COMMON USE CASES: - "How many days until Dec 31?" → from_date="now", to_date="2025-12-31" - "How long since Jan 1?" → from_date="2025-01-01", to_date="now" - "Duration between two dates" → from_date="2025-01-01", to_date="2025-03-15" NOTE: If both parameters are the same (e.g., both "now"), returns an error message. Uses accurate NTP time when "now" is specified.
Get a list of public holidays (and optionally school holidays) for a country and year. Use this tool when the user asks about holidays, days off, or vacation periods. :param country: Country name or ISO code (required). Examples: "Poland", "PL", "United States", "US", "Germany", "DE" Supports common aliases like "UK" for United Kingdom. :param year: Year to get holidays for (optional). Defaults to current year if not specified or 0. Examples: 2026, 2027 :param include_school_holidays: Whether to include school vacation periods (optional). Default is False. Set to True to see school holidays. School holidays are only available for ~36 countries (mostly European). School holidays may vary by region (e.g., different dates for different states/provinces). OUTPUT FORMAT: - Public holidays: Date, name (with local name if different) - School holidays (if requested): Date range, name, regions affected EXAMPLES: - get_holidays(country="Poland") - All public holidays in Poland this year - get_holidays(country="DE", year=2026) - German holidays for 2026 - get_holidays(country="Poland", include_school_holidays=True) - Polish holidays + school vacations NOTE: Public holiday data is available for ~119 countries. School holiday data is available for ~36 countries (mostly European).
Scores are informational only and provided “as is” without warranty. AgentHotspot assumes no liability for actions taken based on these ratings.