Timezone Converter API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 25, 2026

Convert datetime between timezones. List all IANA zones. x402 micropayment.

The publisher's own server: timezone.football

Overview

AI-generated overview

A remote MCP server that converts datetimes between IANA timezones, with DST-aware offsets, billed per call through x402 USDC micropayments.

What you can do
Convert a datetime from one IANA timezone to another, returning the converted time with UTC offset, abbreviation and DST flag (utility_convert_timezone). Accept ISO 8601 or human-readable input and get JSON output. The description also mentions listing all IANA zones, though only the convert tool is documented in the README.
When to use it
Useful when an assistant needs quick, accurate timezone conversion for scheduling meetings, reading log timestamps, coordinating international events or showing local times, without maintaining its own timezone library.
Requirements
A remote SSE endpoint; no local runtime, API key or signup. Each call is paid per use via x402 in USDC on Base L2, so an x402-capable client with a funded wallet is needed to complete the payment challenge. Network access to the endpoint is required.
Before you install
Every call costs money ($0.003 per conversion) and requires a crypto wallet holding USDC on Base; payment is handled by third-party facilitators (Coinbase CDP, PayAI). Requests and datetimes go to an external service. The README also points to a broader marketplace of paid APIs.

Installation

In SourceWeft

  1. Open Timezone Converter API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Ftimezone-converter/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "timezone-converter-api": {
      "type": "sse",
      "url": "https://timezone-converter.api.klymax402.com/mcp"
    }
  }
}

README

Timezone Converter API

[MCP Server] [x402] [License: MIT]

Convert datetime between timezones -- all IANA zones, UTC offset, DST-aware. ISO 8601 input/output. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "timezone-converter": {      "url": "https://timezone-converter.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl -X POST "https://timezone-converter.api.klymax402.com/api/convert" \  -H "Content-Type: application/json" \  -d '{"datetime":"...","from":"...","to":"..."}'# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
utility_convert_timezonePOST/api/convert$0.003Convert a datetime between timezones

utility_convert_timezone

Use this when you need to convert a date/time from one timezone to another. Returns the converted datetime with offset data in JSON.

Parameters

NameTypeRequiredDescription
datetimestringyesDate/time string (ISO 8601 or human-readable, e.g. '2024-01-15T14:30:00')
fromstringyesSource IANA timezone (e.g. America/New_York)
tostringyesTarget IANA timezone (e.g. Europe/Paris)

Example response:

json
{"originalDatetime":"2026-04-13T14:30:00","fromTimezone":"America/New_York","toTimezone":"Europe/Paris","convertedDatetime":"2026-04-13T20:30:00","utcOffset":"+02:00","abbreviation":"CEST","isDST":true}

When to use: scheduling meetings across timezones, converting log timestamps, coordinating international events, and displaying local times.

Not for: currency conversion (use finance_convert_currency), unit conversion (use utility_convert_units), weather data (use data_get_weather).

Example agent prompts

  • "Convert a date/time from one timezone to another"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit 1e48bdf

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Timezone integrations