The first is not knowing what time it is now: get_local_time answers from the machine and get_utc from an NTP server for when the machine's clock is not to be trusted. The second is date arithmetic, and calculate_time_distance is where the business_days and exclude_holidays arguments earn their place — "how many working days until the deadline" is a question that gets answered wrongly far more often than it looks. The location handling states its own precedence, timezone over city over country, so an ambiguous request resolves predictably rather than by guess.
A time and calendar server covering local time, NTP-backed UTC, localisation, date arithmetic and public holidays.
- get_local_time, the current local time and timezone from the machine the server runs on
- get_utc, accurate UTC from an NTP server, with the server selectable
- get_current_time, localised by timezone, city or country — timezone takes priority over city, and city over country — with optional conversion into other calendar systems
- calculate_time_distance between two dates or datetimes in a chosen unit, optionally counting business days only and excluding holidays
- get_holidays for a country and year, optionally including school holidays
- is_holiday, checking a single date against a country or city
Nothing — no account, no key. get_utc reaches an NTP server, so that one needs network access; the others do not.
One command — uvx mcp-simple-timeserver