time — Claude Code MCP server: real clock for your agent

What time does

Language models are bad at local time. Ask one what hour it is in Sydney during a DST shift and you get a confident wrong answer. The time server answers from the IANA timezone database and a city registry, and every response carries a source_url pointing at the matching page.

It runs at https://worldclock.pro/mcp over Streamable HTTP. No API key, no sign-in. Five tools sit behind it: get_current_time for one place or up to 50 at once, convert_time for moving a moment across zones, time_by_coordinates for a latitude and longitude pair, get_dst_transitions for clock-change dates in any year, and search_cities for looking up a city by name. A place can be a city name or alias, an IANA id, an abbreviation like ET, or coordinates.

Know the ceilings before you wire it in. One IP gets 60 calls per 10 seconds; past that the endpoint answers HTTP 429 with a Retry-After header, so a loop over many locations can stall. search_cities caps at 25 matches. Bad input comes back as structured errors such as LOCATION_NOT_FOUND or INVALID_TIMEZONE, which the agent can read and retry with a corrected argument.