World Time MCP Server
Related Servers
Alternatives to World Time MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides current local time and time in any IANA timezone, along with timezone listing and NTP-based time retrieval with clock offset information.4MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to get current time information for any timezone worldwide, including available regions, cities, and ISO 8601 formatted timestamps with timezone offsets.8-
- AlicenseBqualityCmaintenanceEnables converting moments between IANA zones, answering what time it is in one place when it’s a given time in another, and finding overlapping meeting windows for multiple participants’ work hours, all locally via date-fns-tz/Intl.4MIT
- AlicenseAqualityDmaintenanceAccess the time in any timezone and get the current local time142MIT
- AlicenseAqualityCmaintenanceReturns the current date, time, and timezone, optionally for a specified IANA timezone, without network calls or API keys.1MIT
- AlicenseBqualityDmaintenanceProvides current time and timezone conversion using IANA timezone names, enabling LLMs to get time information and convert times between timezones.2MIT
TDQS
Scored across 4 tools
Each tool has a reasonably distinct purpose: get_time for one city's current time, convert_time for translating a specific time between cities, compare_times for a multi-city snapshot, and find_cities for resolving ambiguous names. The only mild overlap is get_time vs. compare_times, since the latter is effectively a batch version of the former, but the singular/plural distinction is easy to infer.
All four tools follow a consistent verb_noun snake_case pattern: get_time, convert_time, compare_times, find_cities. No mixed conventions or vague verbs.
Four tools is a tight, well-scoped surface for a world-time server, and each one earns its place (lookup, single-city time, conversion, multi-city comparison). Nothing appears redundant or missing from a count perspective.
The surface covers the core lifecycle: resolve a city, get current time, convert a time, and compare multiple cities. Minor gaps exist, such as computing elapsed duration or difference between two arbitrary times, but agents can approximate these with convert_time.