Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.MukundaKatta/timezone-mcp

NPM · @MUKUNDAKATTA/TIMEZONE-MCP · SCANNED AUG 6

IANA timezone conversions with real DST rules.

+61 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT OR Apache-2.0).Pass
  • Actively maintained (last published 81 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 188 tokens (~62/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mukundakatta/timezone-mcp

# add to Claude Code
claude mcp add mukundakatta-timezone-mcp -- npx -y @mukundakatta/timezone-mcp
# add to Codex CLI
codex mcp add mukundakatta-timezone-mcp -- npx -y @mukundakatta/timezone-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mukundakatta-timezone-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mukundakatta/timezone-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mukundakatta-timezone-mcp --command npx --arg -y --arg @mukundakatta/timezone-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mukundakatta-timezone-mcp:
    command: "npx"
    args: ["-y", "@mukundakatta/timezone-mcp"]
// mcp.json
{
  "mcpServers": {
    "mukundakatta-timezone-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mukundakatta/timezone-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Aug 26 +1

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

  • 5 Aug 26 +1
    • CVE-2026-69207 no longer affects this package security
    • Known CVEs: fail → partial security
  • 4 Aug 26 0
    • CVE-2026-69207 affects this package: medium security
    • Known CVEs: partial → fail security
  • 3 Aug 26 +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.

  • 2 Aug 26 +59
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Licence: MIT OR Apache-2.0 functional
  • 1 Aug 26 −26
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
  • 31 Jul 26 +25
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −21
    • Malware scan: pass → unverified security
    • Dependency health: partial → unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Aug 2026 · Analysed npm/@mukundakatta/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 94 packages
Packages resolved 94
Deprecated 94
Stale 29
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~188 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
convert_tz ~100

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.

NameTypeReqDescription
instantstringyesISO 8601 UTC instant, e.g. '2026-05-10T13:45:00Z'.
timezonestringyesIANA timezone, e.g. 'America/New_York', 'Asia/Kolkata'.

No output schema declared.

No examples provided.

now_in ~35

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

NameTypeReqDescription
timezonestringyes

No output schema declared.

No examples provided.

tz_offset ~53

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.

NameTypeReqDescription
instantstringyes
timezonestringyes

No output schema declared.

No examples provided.