Timezone Truth MCP server

• convert_timeFree

  Convert a wall-clock time between two IANA timezones, and report the ways the conversion can be wrong. ALWAYS use this instead of doing the arithmetic. Timezone conversion looks like addition and is not: the mapping from a local time to an instant is not a function. - On the spring-forward date, an hour of local time DOES NOT EXIST. Asked to convert 02:30 on that date, a model will return a plausible timestamp for a time that never happens. This tool returns null and says why. - On the fall-back date, an hour happens TWICE. There are two correct answers an hour apart; this returns both rather than silently choosing. - The gap between two zones is not constant. Zones start and end daylight saving on different dates, so a cached offset is wrong for weeks each year. - Not all offsets are whole hours: India is +05:30, Nepal +05:45. Input: `time` must be YYYY-MM-DD HH:MM (or with T, and optional seconds) — free-form dates are refused rather than guessed. `from` and `to` must be full IANA names such as "America/New_York". ABBREVIATIONS ARE REJECTED, deliberately, even though most runtimes accept them. Node resolves "BST" to Bangladesh Standard Time (UTC+06:00) when nearly everyone writing it means British Summer Time (UTC+01:00) — a five-hour error that yields a perfectly plausible timestamp. Same for CST, IST, PST, and EST. Returns: the chosen UTC instant (null if the local time does not exist), every candidate instant, both zone readings with the offset and abbreviation that applied on THAT date, the difference between the zones, upcoming clock changes for both, and warnings. Check `warnings` for severity "error" before using the result.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1555ms20/20
• Tool poisoning1 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

75/100

higher than 45% of 48,243 servers

Tools

1

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

850 ms

faster than 17% of 30,027 servers

Grade history

• 2026-10-16restoreC → Bscore 75

Timezone Truth: common questions

Is Timezone Truth MCP server safe?

Mostly: it is graded B (75/100). Read the Timezone Truth safety report

How do I install Timezone Truth?

It runs remotely at timezone-truth.gumballtools.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Timezone Truth need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Timezone Truth maintained?

The latest release is v0.1.0.

Is Timezone Truth up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Timezone Truth compare with other MCP servers?

safety score 75/100 (higher than 45% of 48,243 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.