# io.github.jordanburke/temporal-mcp-server (remote · time.somamcp.com)

Time, timezone and duration tools — IANA zones, conversion, DST-correct date arithmetic.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `time.somamcp.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/jordanburke-temporal-mcp-server/time.md), [page](https://verifymcp.io/servers/jordanburke-temporal-mcp-server/time)
- npm · `temporal-mcp-server`: 81/100, [markdown](https://verifymcp.io/servers/jordanburke-temporal-mcp-server/temporal-mcp-server.md), [page](https://verifymcp.io/servers/jordanburke-temporal-mcp-server/temporal-mcp-server)

## Channel facts

- Endpoint: `https://time.somamcp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.3`

## 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-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 520 tokens (~104/item across 5 items; 5 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.jordanburke/temporal-mcp-server server?

io.github.jordanburke/temporal-mcp-server is a hosted endpoint at https://time.somamcp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http jordanburke-temporal-mcp-server 'https://time.somamcp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jordanburke-temporal-mcp-server": {
      "url": "https://time.somamcp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jordanburke-temporal-mcp-server": {
      "type": "http",
      "url": "https://time.somamcp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jordanburke-temporal-mcp-server]
url = "https://time.somamcp.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jordanburke-temporal-mcp-server": {
      "type": "remote",
      "url": "https://time.somamcp.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jordanburke-temporal-mcp-server --url 'https://time.somamcp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jordanburke-temporal-mcp-server:
    url: "https://time.somamcp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jordanburke-temporal-mcp-server": {
      "Transport": "http",
      "Url": "https://time.somamcp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jordanburke-temporal-mcp-server -t streamable-http -u 'https://time.somamcp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jordanburke-temporal-mcp-server": {
      "type": "http",
      "url": "https://time.somamcp.com/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-11-04 (score 64, +1)

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

### 2026-11-02 (score 63, +1)

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

### 2026-10-30 (score 62, +1)

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

### 2026-10-29 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 61)

First indexed and scored.

## MCP tools (5)

### `info` (~28 tokens)

Returns identity and build information for this server (name, version, build commit, runtime, capability counts)

### `get_current_time` (~59 tokens)

Return the current time as an epoch, a UTC ISO-8601 timestamp, and the wall-clock time in a given timezone.

Input parameters:

- `timezone` (string): IANA timezone identifier, e.g. 'America/New_York'. Defaults to UTC.

### `convert_timezone` (~107 tokens)

Render an ISO-8601 timestamp as wall-clock time in a target timezone.

Input parameters:

- `isoTimestamp` (string, required): ISO-8601 timestamp to convert, e.g. '2026-08-17T14:30:00Z'.
- `sourceTimezone` (string): IANA timezone used to interpret `isoTimestamp` when it carries no 'Z' or offset. Ignored otherwise. Defaults to UTC.
- `targetTimezone` (string, required): IANA timezone identifier to render in.

### `add_duration` (~203 tokens)

Add an ISO-8601 duration to a timestamp, in a timezone. Date units (Y/M/D) are calendar-aware: P1D across a DST boundary keeps the same wall-clock time the next day, and P1M on Jan 31 clamps to the end of February. Time units (H/M/S) are exact elapsed time, so PT24H really is 24 hours. Prefix the duration with '-' to subtract.

Input parameters:

- `duration` (string, required): ISO-8601 duration, e.g. 'P1D', 'PT30M', 'P1Y2M3DT4H5M6S', or '-P1W'.
- `isoTimestamp` (string, required): ISO-8601 timestamp to shift.
- `timezone` (string): IANA timezone governing the arithmetic — calendar units are applied to this zone's wall clock, and a timestamp with no 'Z' or offset is read as wall-clock time here. Defaults to UTC.

### `time_between` (~123 tokens)

Exact elapsed time between two ISO-8601 timestamps, broken into days/hours/minutes/seconds plus a human-readable summary. All components share one sign, so they sum correctly; `direction` is 'past', 'future', or 'same'.

Input parameters:

- `from` (string, required): Start of the interval, as an ISO-8601 timestamp.
- `timezone` (string): IANA timezone used to interpret timestamps that carry no 'Z' or offset. Defaults to UTC.
- `to` (string, required): End of the interval, as an ISO-8601 timestamp.

## Diagnostics

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

## Score history

- 2026-11-05: 64
- 2026-11-04: 64
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 62
- 2026-10-29: 61
- 2026-10-28: 61

## Common questions

### What is the io.github.jordanburke/temporal-mcp-server server?

io.github.jordanburke/temporal-mcp-server is listed in the public MCP registry as io.github.jordanburke/temporal-mcp-server. Time, timezone and duration tools, IANA zones, conversion, DST-correct date arithmetic. This page covers its hosted endpoint (https://time.somamcp.com/mcp).

### Is the io.github.jordanburke/temporal-mcp-server server safe to use?

io.github.jordanburke/temporal-mcp-server scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.jordanburke/temporal-mcp-server server expose?

io.github.jordanburke/temporal-mcp-server exposes 5 tools: info, get_current_time, convert_timezone, add_duration, time_between. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.

### Does the io.github.jordanburke/temporal-mcp-server server require authentication?

No. We connected to io.github.jordanburke/temporal-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.jordanburke/temporal-mcp-server server still maintained?

io.github.jordanburke/temporal-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the io.github.jordanburke/temporal-mcp-server server?

VerifyMCP ran 11 checks on io.github.jordanburke/temporal-mcp-server, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.jordanburke/temporal-mcp-server: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://time.somamcp.com/mcp
- Repository: https://github.com/jordanburke/temporal-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/jordanburke-temporal-mcp-server/time.xml
- Changelog JSON feed: https://verifymcp.io/servers/jordanburke-temporal-mcp-server/time/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/jordanburke-temporal-mcp-server/time.json
- HTML version of this page: https://verifymcp.io/servers/jordanburke-temporal-mcp-server/time