Timezone Offset Engine MCP for AI. Calculate accurate global time offsets, DST included.

Q: How do I use gettimezoneoffset to check DST?

Just call gettimezoneoffset and pass an optional ISO 8601 datetime. The tool response includes a flag for each zone, confirming if it's operating under Daylight Saving Time at that specific time.

Q: Is gettimezoneoffset better than simple date math?

Absolutely. Simple math fails when DST changes occur. gettimezoneoffset uses the full IANA database to calculate time offsets accurately, regardless of how complex the zone rules are.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Connect to your AI in seconds.

Timezone Offset Engine calculates the exact time difference between any two IANA-compliant zones at a specific moment. It handles all Daylight Saving Time (DST) transitions worldwide, using the full IANA database for guaranteed accuracy.

Your AI client calls this tool to get precise offsets in hours and minutes, ensuring your scheduling or data logic never gets confused by DST changes.

What your AI can do

Get timezone offset

Pass two IANA timezone names and an optional ISO 8601 datetime. The engine returns the precise offset in hours/minutes and DST status. Use this when you need to verify time differences.

Determine Offset by Date

Pass two IANA timezone names and a specific date/time to calculate the exact offset between them.

Check DST Status

The tool reports whether or not each specified zone is currently observing Daylight Saving Time at the requested moment.

Calculate Local Times

You can determine the local time in two different zones based on a single starting timestamp.

Cross-Boundary Checking

It handles dates that cross major DST transitions, ensuring the offset calculation remains valid even when rules change mid-year.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

Timezone Offset Engine: 1 Tool for Global Timing

This single tool lets your AI client calculate precise offsets between any two IANA timezones, handling DST transitions worldwide.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Timezone Offset Engine on Vinkius

Get Timezone Offset

Pass two IANA timezone names and an optional ISO 8601 datetime. The engine returns the precise offset in hours/minutes and DST status. Use...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The Timezone Offset Engine integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "timezone-offset-engine": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the Timezone Offset Engine tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"timezone-offset-engine": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with Timezone Offset Engine, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Luxon. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 1 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Scheduling global meetings shouldn't feel like a geopolitical puzzle.

Right now, figuring out if 9 AM in New York is the same as 2 PM somewhere else involves opening three different calendars, cross-referencing local time zone rules, and manually checking for Daylight Saving Time changes. It's a tedious process that requires constant double-checking—and it’s easy to get off by an hour.

With this MCP server, you simply ask your agent: 'What is the offset between America/Los_Angeles and Europe/London on June 20th?' The tool runs the calculation instantly. You get a single, verifiable answer that accounts for DST rules, eliminating all ambiguity.

Timezone Offset Engine MCP Server: Get precise offsets from chat.

You no longer have to copy-paste zone names into separate calculators or rely on general LLM knowledge. You just need to tell your agent the two IANA zones and a date, letting `get_timezone_offset` handle all the heavy lifting of time math.

The difference is verifiable accuracy. It's not an estimate; it’s a calculation based on the full IANA database for that exact moment in history.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

What your AI can actually do with this

You're dealing with time zones? Forget what your AI client thinks it knows. This Timezone Offset Engine is built for precision. It runs on the full IANA timezone database, so you never worry about Daylight Saving Time messing up your logic.

Your agent uses get_timezone_offset by passing two specific IANA zone names and an optional ISO 8601 timestamp. The tool immediately spits out the exact offset in hours and minutes for that moment, telling you if it's even observing DST. It’s pure, verifiable time math.

When you need to figure out how far apart São Paulo and London are on a specific day—say, July 15th—you just pass those two zones and the date. The engine handles every rule change that might happen between them. You don't gotta guess what DST does; it tells you exactly where the time difference lands at that precise moment.

If your workflow requires checking if a zone is currently running on DST, the tool reports that status directly when you call get_timezone_offset. It tells you whether each specified location is observing Daylight Saving Time for the requested timestamp. This means your agent knows instantly if it needs to adjust its internal logic for those zones.

The engine lets you calculate local times in two different zones based on a single starting point. You give it one timestamp, and it figures out what time that'll be locally in both of the specified regions. It’s perfect for scheduling tasks across multiple continents.

It handles date ranges that cross major DST boundaries flawlessly. If your calculation spans days where the rules change—for example, crossing a spring forward or fall back day—the offset remains valid because the system uses the comprehensive IANA database. You're safe from those tricky mid-year rule changes.

When you call get_timezone_offset, it gives you more than just an offset number; it delivers that precise offset in hours and minutes, along with a boolean flag confirming if each zone is currently observing DST at the specified time. This level of detail keeps your data pipelines running clean and accurate.

You'll use this when you need to verify complex time differences across international lines.

It works by consuming two IANA timezone names—like America/New_York and Europe/Paris—and an optional ISO 8601 datetime string. The tool takes these inputs and returns the exact offset, which is crucial for any scheduling agent or data processing pipeline that can't afford to get confused by time changes.

You pass two zones and a specific timestamp when you want to determine the precise offset between them at that date. This ensures your system calculates the difference correctly even if one zone observes DST while the other doesn't, or if both are changing rules on the same day.

The function determines the local time in two different zones from just one starting timestamp. You give it a moment, and it spits out what time that is locally for both specified locations simultaneously. This feature eliminates guesswork when coordinating events across time zones.

This tool's ability to handle cross-boundary checking means you don't have to write complex date logic yourself. If your data crosses the line of a major DST transition, like moving from one calendar year to another or spanning an entire seasonal change, the offset calculation stays solid and reliable.

Built · Hosted · Managed by Vinkius Timezone Offset Engine - Calculate Time Zone Offsets

Server ID 019e38fc-37cd-71aa-9248-5544fa1b0d67

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is: you get a verifiable time difference that accounts for global time rules and Daylight Saving Time changes.

Your AI client calls get_timezone_offset, providing two IANA zone names (like "Asia/Tokyo" and "America/Los_Angeles").

You pass an optional ISO 8601 datetime string to specify the exact moment for calculation.

The engine runs the query, returning the precise offset in hours/minutes, along with DST status flags for both zones.

What Changes When You Connect

Stop worrying about Daylight Saving Time shifts. The get_timezone_offset tool guarantees the offset calculation is correct for any date, even when zones transition between standard and daylight time.

Keep your data pipelines clean. Instead of guessing time differences, you use this tool to get a verifiable offset in hours and minutes, which keeps all synchronized records accurate.

Schedule meetings with confidence. You can feed the agent two location names and a date, and it returns the precise offset for that specific moment, letting you suggest meeting times that work globally.

Handle global logs without breakage. If your data comes from multiple time zones (e.g., Tokyo and London), get_timezone_offset tells your agent the true difference, so your records align correctly.

Maintain code reliability. By calling get_timezone_offset, you offload the complex logic of IANA timezone rules to a dedicated engine, making your application less brittle.

See it in action

01 01

Scheduling an international deadline

A global program manager needs to set a submission deadline for London and Sydney. They ask their agent: 'What is the offset between Europe/London and Australia/Sydney on November 1st?' The agent calls get_timezone_offset, gets the accurate offset, and informs the manager of the precise time difference, avoiding confusion over changing rules.

02 02

Aligning multi-region log files

A DevOps engineer reviews server logs from two different data centers (America/Chicago and Asia/Shanghai). They ask their agent to calculate the offset for a specific failure time. The agent uses get_timezone_offset with the timestamp, giving the exact hours difference needed to correctly sequence the events.

03 03

Comparing event times across zones

A data scientist needs to compare two marketing campaign start dates in New York and São Paulo. They ask their agent: 'What's the offset between America/Sao_Paulo and America/New_York on July 15?' The agent runs get_timezone_offset, confirming the precise difference, which is critical for reporting accurate global metrics.

04 04

Validating a complex API requirement

A backend developer needs to write code that checks if a user input time falls within an acceptable window across two zones. They use get_timezone_offset to determine the required offset boundaries for their validation logic, ensuring the client-side and server-side clocks match.

The honest tradeoffs

Assuming static time difference

Anti-pattern

Using simple math (e.g., 'London is 5 hours ahead of Paris') or relying on built-in LLM knowledge for time differences.

The Fix

Always use get_timezone_offset. You must pass the specific IANA zone names and, if possible, a precise date/time to account for DST shifts. Never trust general rules; check the tool.

Forgetting Daylight Saving Time

Anti-pattern

Asking for the difference between two zones in March or November when both might be transitioning their clocks.

The Fix

The get_timezone_offset tool handles this automatically. Just pass the date and let it calculate whether DST is active for each zone at that moment.

Using incomplete time data

Anti-pattern

Only providing two city names without knowing which specific date you care about.

The Fix

Provide both IANA zone identifiers AND an ISO 8601 datetime. This forces the engine to calculate the offset for a single, verifiable point in time.

When It Fits, When It Doesn't

Use this Timezone Offset Engine if your task involves comparing or scheduling events across different global zones at a specific moment. You need guaranteed accuracy that accounts for Daylight Saving Time (DST) and uses the full IANA database.

Don't use this if:
1. You just want to know the general time difference between two major cities, regardless of date. Simple search results or basic math will suffice.
2. Your task only deals with a single timezone.
3. You are building internal clock logic and need to manage multiple complex sources (in which case you should look into dedicated database extensions rather than just this tool).

If the time element is the most critical part of your workflow, use get_timezone_offset.

Questions you might have

How do I use get_timezone_offset to check DST? +

Just call get_timezone_offset and pass an optional ISO 8601 datetime. The tool response includes a flag for each zone, confirming if it's operating under Daylight Saving Time at that specific time.

Can get_timezone_offset handle non-standard zones? +

Yes. It supports all 400+ IANA timezones, meaning it can calculate offsets for nearly any location on Earth, provided you use the correct zone identifier.

Is get_timezone_offset better than simple date math? +

Absolutely. Simple math fails when DST changes occur. get_timezone_offset uses the full IANA database to calculate time offsets accurately, regardless of how complex the zone rules are.

What format should I use for get_timezone_offset's date input? +

Use ISO 8601 datetime format (e.g., '2025-07-15T12:00:00Z'). This gives the engine the specific moment it needs to calculate the offset for.

How does `get_timezone_offset` handle malformed or non-existent IANA zone names? +

It returns a specific error message detailing the exact zone name that failed validation. The engine won't guess; it throws an explicit failure when a provided timezone doesn't match the official database.

What is the expected performance or rate limit when calling `get_timezone_offset` frequently? +

The server handles high-volume requests efficiently. While specific operational limits depend on your Vinkius subscription tier, it's engineered for reliable, enterprise-level data throughput.

Can `get_timezone_offset` calculate the time difference without providing an ISO 8601 datetime? +

Yes. If you omit the specific date and time input, it calculates the maximum potential offset range between the two zones based on their established rules.

What underlying library does `get_timezone_offset` use, and why should I trust its calculations? +

It uses Luxon with the full, maintained IANA timezone database. This isn't a simple calculation; it relies on globally vetted standards for timekeeping.

Does it handle Daylight Saving Time? +

Yes. This is the primary reason this tool exists. It calculates offsets at the exact moment you specify, correctly accounting for all DST transitions worldwide.

What datetime format should I use? +

ISO 8601 format: YYYY-MM-DDTHH:mm:ss (e.g. '2025-07-15T14:00:00'). If omitted, the engine uses the current moment.

How many timezones are supported? +

All 400+ IANA timezone identifiers, including regional variants like America/Argentina/Buenos_Aires and special zones like UTC and GMT.

Connect to your AI in seconds.

Get timezone offset

Timezone Offset Engine: 1 Tool for Global Timing

Make your AI actually useful.

Get Timezone Offset

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Works with Claude, ChatGPT, Cursor, and more

Scheduling global meetings shouldn't feel like a geopolitical puzzle.

Timezone Offset Engine MCP Server: Get precise offsets from chat.

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

See it in action

Scheduling an international deadline

Aligning multi-region log files

Comparing event times across zones

Validating a complex API requirement

The honest tradeoffs

Assuming static time difference

Forgetting Daylight Saving Time

Using incomplete time data

When It Fits, When It Doesn't

Questions you might have