Summary
A model does not know what day it is — this tells it.
Sessions go wrong routinely because the model assumes its training cutoff is today. One tool fixes that. The design choice worth noticing is the plural sourcing: 4 sources with automatic fallback, rather than one API that can be down or wrong.
What it is
A small Node server that answers one question — what time is it in UTC — and does not trust a single source for the answer. It checks WorldClockAPI and the HTTP `Date` headers from WorldClock, Google and GitHub, falling back automatically between them.
What you get
- The current UTC time as ISO 8601, a Unix timestamp, a human-readable sentence, date only, or time only — `get_utc_time`
- Automatic fallback across 4 sources, so one unreachable service does not break the answer
- A prebuilt `dist/index.js`, so there is no compile step between cloning and running
Requirements
No account and no key. Node.js version 14 or higher, and an MCP-compatible client. Clone the repository and point the client at `dist/index.js`; the package is `getutc-mcp` 1.0.0.