MCP-timeserver
Related Servers
Alternatives to MCP-timeserver
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides current local time and time in any IANA timezone, along with timezone listing and NTP-based time retrieval with clock offset information.427 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceProvides time zone management utilities including retrieving current time in any global time zone and converting time between different time zones with automatic daylight saving time handling.125 npmMIT
- FlicenseBqualityDmaintenanceProvides current time and timezone conversion using IANA timezone names, with automatic system timezone detection.2-
- AlicenseBqualityDmaintenanceProvides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.2MIT
- 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-
- 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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clear, so an agent cannot misselect between non-existent alternatives.
The single tool name follows a clear verb_noun pattern (get-current-time), and with no other tools to compare, there is no inconsistency. The naming is straightforward and predictable.
A single tool for a time server feels thin and under-scoped, as it only provides current time retrieval without obvious related operations like time conversion, formatting, or scheduling. This minimal set may limit functionality for typical time-related tasks.
The tool surface is severely incomplete for a time server domain, lacking basic operations such as converting between timezones, formatting times, or handling dates. It covers only a narrow slice of potential time-related functionality, likely causing agent failures in broader scenarios.