mcp server
temporal-mcp
Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.
Description as published by the maintainer. Source
- version 0.2.0
- active
active — Registry entry last updated 2026-05-13.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
temporal_peek(tz_name, client_id, thread_key, tz_offset_minutes)- Read the current temporal snapshot for a thread WITHOUT advancing state. Use this when you want the gap delta but the call is not the canonical per-turn event.
temporal_tick(tz_name, client_id, thread_key, tz_offset_minutes)- Advance the temporal clock for a thread and return a snapshot (now / prev / gap / day_rollover / fresh_thread). Call once per user turn. Pass a stable `thread_key` (e.g. the conversation ID) so gap deltas remain meaningful across page reloads.
Last successful function declaration observed on . Source: https://temporal-mcp.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://temporal-mcp.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-13 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-13 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | temporal-mcp.dev | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | temporal-mcp.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json