Asking a model what today's date is gets you its training cutoff, which quietly breaks anything that reasons about deadlines or recency. This closes that hole in the smallest possible way — a formatted JST string on request. The scope is genuinely fixed at Japan Standard Time, so treat it as a fit for JST work rather than a general clock.
A single-purpose server for a gap models genuinely have: they do not know what time it is. It answers with the current Japan Standard Time as a `YYYY-MM-DD HH:MM:SS JST` string. No parameters, no configuration, no network calls.
- `get_current_time` returns the current JST time as `YYYY-MM-DD HH:MM:SS JST`
- No parameters to pass and nothing to configure
- Runs entirely locally — no account, no key, no outbound request
Install the package `what-time-is-it-now-mcp` (version 0.1.0) and point your client at the `what-time-is-it-now-mcp` command over stdio, or add it in Claude Code with `claude mcp add what-time-is-it-now-mcp`. Nothing else. Output is fixed to Japan Standard Time, so if you need another zone this is not the one.
One command — claude mcp add what-time-is-it-now-mcp
