MCP.Market

Timezone MCP server

by MukundaKatta·io.github.MukundaKatta/timezone-mcp·v0.1.0

IANA timezone conversions with real DST rules.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars26 downloads/wk

Reviews

Write one

Nobody has reviewed Timezone yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Timezone tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • convert_tz

    Convert a UTC ISO instant into a given IANA timezone. Returns the local ISO string with offset, the offset in minutes, and the formatted offset string. Handles DST automatically.

  • now_in

    Get the current local time in a given IANA timezone. Same return shape as convert_tz.

  • tz_offset

    Get the UTC offset for a timezone at a specific instant. Useful for DST boundary checks: pass an instant a few hours apart to detect a DST transition.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Timezone compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 48,273 servers
Tools
3
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
26
more than 14% of 11,915 servers with a package

What its tools let an agent do: 3 read

Install Timezone in Claude Code, Cursor or VS Code

Runs npx -y @mukundakatta/timezone-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add timezone-mcp -- npx -y @mukundakatta/timezone-mcp
Add to Cursor

What the publisher says

From the Timezone repository's README, as published. We do not edit it. Read it on GitHub

mcp-stack

Fourteen small MCP servers for everyday LLM / RAG / agent work. Each ships independently on npm, listed in the official MCP Registry, and is callable from Claude Desktop, Cursor, Cline, Windsurf, Zed, and any other MCP-compatible client.

RAG / agent helpers

Reliable transforms LLMs reach for tools instead of imagining

Sibling libraries

The first four wrap or re-implement logic from the user's Rust + Python work:

ragdrift-py (PyPI) — five-dimensional drift detection

  • ragdrift (crates.io) /

stopstream, citecite, ragmetric — pure-Rust crates from the rust-llm-stack workspace

  • embedrank, promptbudget,

The MCP servers are independent: they implement the logic they need in plain JavaScript so installing them doesn't pull a Rust toolchain.

Install (any of them)

Add to your MCP client config. Example for Claude Desktop:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Timezone: common questions

Is Timezone MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Timezone safety report
How do I install Timezone?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Timezone need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Timezone maintained?
The last commit was 65 days ago (2026-08-29). The latest release is v0.1.0.
How does Timezone compare with other MCP servers?
safety score 92/100 (higher than 90% of 48,273 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from MukundaKatta →