# temporal-mcp (remote · temporal-mcp.dev)

Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `temporal-mcp.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp.md), [page](https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp)
- pypi · `temporal-mcp`: 39/100, [markdown](https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp-2.md), [page](https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp-2)

## Channel facts

- Endpoint: `https://temporal-mcp.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 297 tokens (~148/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http mirrorethic-temporal-mcp https://temporal-mcp.dev/mcp
```

### Codex

```toml
[mcp_servers.mirrorethic-temporal-mcp]
url = "https://temporal-mcp.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mirrorethic-temporal-mcp": {
      "type": "remote",
      "url": "https://temporal-mcp.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mirrorethic-temporal-mcp --url https://temporal-mcp.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mirrorethic-temporal-mcp:
    url: "https://temporal-mcp.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "mirrorethic-temporal-mcp": {
      "type": "http",
      "url": "https://temporal-mcp.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (2)

### `temporal_tick` (~224 tokens)

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.

Input parameters:

- `client_id` (string): Namespace tag (e.g. 'caweb', 'cursor'). Defaults to 'mcp'.
- `thread_key` (string): Stable thread identifier within this client. For claude.ai web use the conversation ID; for other MCP clients any caller-stable string. If omitted, falls back to the Mcp-Session-Id header.
- `tz_name` (string): Display name for the timezone (e.g. 'MDT'). Cosmetic; appears in the rendered header.
- `tz_offset_minutes` (integer): Caller's UTC offset in minutes (e.g. -360 for MDT). Used for day_rollover detection and header formatting. Defaults to 0 (UTC) so day rollover is always honest even if the caller forgets to pass one.

### `temporal_peek` (~73 tokens)

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.

Input parameters:

- `client_id` (string)
- `thread_key` (string)
- `tz_name` (string)
- `tz_offset_minutes` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 64
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://temporal-mcp.dev/mcp
- Authorisation metadata: https://temporal-mcp.dev/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/MirrorEthic/temporal-mcp
- Website: https://temporal-mcp.dev/
- Changelog RSS feed: https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mirrorethic-temporal-mcp/temporal-mcp