Skip to content

temporal-mcp-server

io.github.jordanburke/temporal-mcp-serverjordanburkestreamable-httpv0.3.1Scanned

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

5 tools: 1 do something that can't be undone, 2 change things and 2 only read.

Tools: 0 delete, 1 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the temporal-mcp-server can do

The temporal-mcp-server is published by the GitHub account jordanburke. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (time_between) and create or change data (2 tools: convert_timezone and add_duration), but cannot delete data. 2 tools only read.

1 tool reads private data (info); 1 tool can send data out of your system (time_between).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.3.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Can't be undone 1Claude Code: ask
  • time_betweenExact elapsed time between two ISO-8601 timestamps, broken into days/hours/minutes/seconds plus a human-readable summary.Can send data outNo findings

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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'.
Changes things 2Claude Code: ask
  • add_durationAdd an ISO-8601 duration to a timestamp, in a timezone.No findings

    Why it is in this group

    • The name "add_duration" says "add": a word for a change.
    Description, as the server wrote it
    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.
  • convert_timezoneRender an ISO-8601 timestamp as wall-clock time in a target timezone.No findings

    Why it is in this group

    • The name "convert_timezone" says "convert": a word for a change.
    Description, as the server wrote it
    Render an ISO-8601 timestamp as wall-clock time in a target timezone.
Only reads 2Show 2 read-only tools
  • get_current_timeReturn the current time as an epoch, a UTC ISO-8601 timestamp, and the wall-clock time in a given timezone.No findings

    Why it is in this group

    • The name "get_current_time" says "get": a word for reading.
    Description, as the server wrote it
    Return the current time as an epoch, a UTC ISO-8601 timestamp, and the wall-clock time in a given timezone.
  • infoReturns identity and build information for this server (name, version, build commit, runtime, capability counts)Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "commit": it reads repositories.
    Description, as the server wrote it
    Returns identity and build information for this server (name, version, build commit, runtime, capability counts)

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://time.somamcp.com/mcp: tools/list returned 5 tools to an anonymous client, including time_between (irreversible), convert_timezone (write), add_duration (write)

    What this check looks for

Posture changes

  1. Nov 12, 2026
    • Protocol version: 2025-11-25 to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Protocol version: 2025-11-25 -> 2025-06-18.View diff
    • Protocol version: 2025-11-25 to 2025-06-18
  2. Tools5 changed.~5 changedView diff

Install

Pinned to version 0.3.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http temporal https://time.somamcp.com/mcp
claude mcp add --transport http temporal https://time.somamcp.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__temporal__info",
      "mcp__temporal__get_current_time"
    ],
    "ask": [
      "mcp__temporal__convert_timezone",
      "mcp__temporal__add_duration",
      "mcp__temporal__time_between"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as temporal. Review it before you use it.

Capability tags behind 2 rules
  • mcp__temporal__info private-data
  • mcp__temporal__time_between outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.jordanburke/temporal-mcp-server/verify?hash=3baebb16b400f0b9d19ebbd40f002a7a2a1c0bed847753221294418ae2ec3aef" | jq -e '.changed == false'

Pinned hash 3baebb16b400, from Nov 15, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.jordanburke/temporal-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.jordanburke/temporal-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.jordanburke/temporal-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.jordanburke/temporal-mcp-server)

Source: MCP Registry · repository. Synced Nov 15, 2026, 22:18 UTC.

temporal-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the temporal-mcp-server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the temporal-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the temporal-mcp-server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: time_between.

What tools does the temporal-mcp-server have?

5 tools: 1 irreversible, 2 write, 2 read. time_between, convert_timezone, add_duration, info and get_current_time.

Does the temporal-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the temporal-mcp-server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): time_between.

Has the temporal-mcp-server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.