How do I install Clockport?

Clockport is a local plugin. Install it using npm package: @reneturcios/clockport and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Clockport safe to use?

Clockport scored 6.5/10 (moderate risk) in MCP Marketplace's automated security scan. It has 2 high or critical findings to review. It's listed, but review the security report on this page before installing.

What AI apps work with Clockport?

Clockport uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Clockport MCP Server

by CloudCorpRecords

Developer ToolsModerate6.5MCP RegistryLocal

Free

Server data from the Official MCP Registry

Current time and timezone conversion for any IANA zone.

About

Current time and timezone conversion for any IANA zone.

Security Report

6.5

Moderate6.5Moderate Risk

clockport is a small, well-scoped timezone utility that uses only Node's Intl API and the MCP SDK, with no network calls, file access, shell execution, or credential handling. Inputs are validated with zod and a strict HH:MM regex, and the test suite covers DST and edge cases. No security findings were identified; the only observation is that the server requires no authentication, which is appropriate for a stateless local clock tool. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

system_info

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-clockport": {
      "args": [
        "-y",
        "@reneturcios/clockport"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

clockport

clockport tells you what time it is somewhere else, and what a given clock time in one place corresponds to in another. It answers two questions — "what time is it in Tokyo right now?" and "my call is at 12:00 New York time, what is that in London?" — from the command line or as an MCP server for agents.

All zone handling uses the IANA timezone database behind Node's Intl support, so daylight-saving changes are handled by the platform rather than by a fixed offset table.

Install

npx @reneturcios/clockport now Europe/London

Or run the container image:

docker run -i ghcr.io/cloudcorprecords/clockport

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

# Current time in a zone
clockport now America/New_York
# 2026-01-15 07:00:00 (America/New_York, 2026-01-15T07:00:00-05:00)

# Convert a time between zones
clockport convert America/New_York 12:00 Europe/London
# 2026-10-26 12:00 America/New_York -> 2026-10-26 17:00 Europe/London (+5h)

# Machine-readable output
clockport now Asia/Tokyo --json
clockport convert UTC 09:30 Asia/Kolkata --json

clockport --version

Exit codes: 0 on success, 1 when a zone or time cannot be handled (the error names the problem), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

npx -y @reneturcios/clockport mcp

MCP client configuration:

{
  "mcpServers": {
    "clockport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/clockport", "mcp"]
    }
  }
}

Tools

Tool	Input	What it returns
`get_current_time`	`timezone` (string, required) — IANA timezone name	The current time in that zone: wall-clock rendering, ISO 8601 form with offset, weekday, UTC offset in minutes, and whether DST is in effect.
`convert_time`	`source_timezone` (string, required), `time` (string, required, `HH:MM` 24-hour), `target_timezone` (string, required)	The requested time rendered in the target zone, with the target date (which may differ from the source date), an ISO 8601 form, and the signed offset difference.

Unknown timezone names and times that are not valid HH:MM values are reported as tool errors rather than guessed at.

Reference date for conversions

convert_time takes a time of day but no date. Conversions therefore use today's date — the current calendar date in the source zone — as the reference date. This matters around daylight-saving transitions, where the offset difference between two zones can change from one week to the next; the result always reflects the difference in force today. The reference date used is included in every conversion result.

Development

npm install
npm run build   # tsc -> dist/
npm test        # node test runner over test/*.test.ts, no network
npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.