LO

Low-Latency UTC Time and Timezone Conversion MCP Server

Get accurate UTC time and fast timezone conversions with this low-latency, high-reliability MCP server for seamless time synchronization and conversion.

Quick Install
npx -y @jairampatel/currenttimeutc-mcp

Overview

This Model Context Protocol (MCP) server exposes a simple, standardized interface to obtain accurate UTC time and perform timezone conversions with millisecond precision. It is designed for low-latency access so applications and agents can reliably synchronize clocks, stamp events, or convert timestamps into any IANA timezone without maintaining a local timezone database.

Because the server implements an MCP schema, it fits naturally into AI and agent ecosystems that use MCP to request contextual data. The server focuses on a small, well-defined set of operations (current UTC time, timezone conversions, and a timezone index) so clients can integrate quickly with predictable responses and minimal overhead.

Features

  • Current UTC time with millisecond precision
  • Single and bulk timezone conversions using IANA timezone identifiers
  • List of supported timezones (IANA)
  • Low-latency responses optimized for quick lookups
  • MCP-compliant schema for easy integration into MCP-aware systems
  • Lightweight documentation and schema files in the repository

Service endpoints

Base URLs and documentation:

  • Base URL: https://a.currenttimeutc.com/mcp
  • Schema URL: https://a.currenttimeutc.com/mcp/schema
  • Documentation: https://currenttimeutc.com/mcp
  • GitHub repo (schema + docs): https://github.com/jairampatel/currenttimeutc-mcp

Endpoint summary

EndpointMethodDescription
/mcp/time/utcGETReturn current UTC time (ISO 8601 with milliseconds)
/mcp/time/convertGETConvert a single timestamp from one timezone to another (query params)
/mcp/time/convert/bulkPOSTConvert multiple timestamps in a single request (JSON body)
/mcp/time/zonesGETReturn list of supported IANA timezone identifiers
/mcp/schemaGETRetrieve the MCP schema (JSON)

(If an endpoint is not present in your environment, check the schema URL or repository for exact API shapes.)

Installation / Configuration

No backend installation is required to use the public MCP server — consume the endpoints directly. If you want to configure a client library in your project, set the base URL and request timeout. Example client snippets below show common usage patterns.

cURL — Get current UTC time

curl -sS "https://a.currenttimeutc.com/mcp/time/utc" \
  -H "Content-Type: application/json"

cURL — Convert a single timestamp (ISO 8601)

curl -sS "https://a.currenttimeutc.com/mcp/time/convert?from_tz=America/New_York&to_tz=Europe/London&time=2024-01-15T14:30:00" \
  -H "Content-Type: application/json"

Python (requests)

import requests

BASE = "https://a.currenttimeutc.com/mcp"

# get UTC now
r = requests.get(f"{BASE}/time/utc", timeout=2.0)
print(r.json())

# single conversion
params = {
    "from_tz": "America/New_York",
    "to_tz": "Europe/London",
    "time": "2024-01-15T14:30:00"
}
r = requests.get(f"{BASE}/time/convert", params=params, timeout=2.0)
print(r.json())

JavaScript (fetch)

const BASE = "https://a.currenttimeutc.com/mcp";

async function getUtcNow() {
  const res = await fetch(`${BASE}/time/utc`);
  return res.json();
}

async function convertTime(fromTz, toTz, isoTime) {
  const url = new URL(`${BASE}/time/convert`);
  url.searchParams.set("from_tz", fromTz);
  url.searchParams.set("to_tz", toTz);
  url.searchParams.set("time", isoTime);
  const res = await fetch(url);
  return res.json();
}

Available Resources

Repository contents (schema + docs):

  • schema/v1.json — MCP schema definition for v1.0.0
  • examples/ — cURL, Python, and JS examples
  • README, LICENSE, GitHub Actions to validate schema

Schema versioning

  • v1.0.0 — initial schema (UTC retrieval, single conversion, timezone listing, validation)

Use the schema URL (https://a.currenttimeutc.com/mcp/schema) to programmatically retrieve request/response shapes and validation rules before integrating.

Use Cases

  • Agent timestamping: An AI agent can call /time/utc to attach authoritative UTC timestamps to actions, logs, or observations.
  • Cross-region scheduling: Convert user-local times into server-local times or vice versa when scheduling jobs across timezones (convert from a user’s IANA timezone to the system timezone).
  • Event normalization: Batch-normalize event logs from multiple sources by converting timestamps into UTC or a target timezone using the bulk conversion endpoint.
  • Display conversions in UIs: Fetch a list of supported timezones (/time/zones) to populate dropdowns and convert timestamps on demand.

Concrete example — Bulk conversion (JSON) Request

POST https://a.currenttimeutc.com/mcp/time/convert/bulk
Content-Type: application/json

{
  "items": [
    { "time": "2024-01-15T09:00:00", "from_tz": "America/Los_Angeles", "to_tz": "Europe/Paris" },
    { "time": "2024-01-15T14:30:00", "from_tz": "America/New_York", "to_tz": "Asia/Tokyo" }
  ]
}

Response (example)

{
  "results": [
    { "converted": "2024-01-15T18:00:00+01:00", "item_index": 0 },
    { "converted": "2024-01-16T03:30:00+09:00", "item_index": 1 }
  ]
}

Notes

  • Times should use ISO 8601 where possible; conversions follow IANA timezone rules (including DST).
  • This repository provides schema and documentation only — the GitHub project does not include backend implementation code. For service-level issues, contact the service maintainers listed on the project

Common Issues & Solutions

I received a GitHub issue notifying me that my project is listed on Spark and asking me to claim the listing. I'm unsure if the message is legitimate and whether I should sign in and grant GitHub access.

✓ Solution

I ran into this too! It was legitimate in my case — I opened the provided asset URL and verified the spark.entire.vc domain and the exact repo slug before signing in. I signed in with GitHub, confirmed the OAuth scopes requested, and verified I had push access to the repository. After clicking Claim, I edited the title/description, saved changes, and added the "Listed on Spark" badge to our README. If you're hesitant, double-check the URL, inspect the OAuth consent screen, and only grant access if the GitHub scopes are appropriate; otherwise comment/close the issue.