# weltze.it Zeitzonen (remote · weltze.it)

Current time, time differences, DST changes and time conversion for any city or IANA time zone.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `weltze.it`: 65/100 (this document), [markdown](https://verifymcp.io/servers/it-weltze-weltze/weltze.md), [page](https://verifymcp.io/servers/it-weltze-weltze/weltze)

## Channel facts

- Endpoint: `https://weltze.it/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 463 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the weltze.it Zeitzonen MCP server?

weltze.it Zeitzonen is a hosted endpoint at https://weltze.it/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http it-weltze-weltze 'https://weltze.it/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "it-weltze-weltze": {
      "url": "https://weltze.it/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "it-weltze-weltze": {
      "type": "http",
      "url": "https://weltze.it/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.it-weltze-weltze]
url = "https://weltze.it/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "it-weltze-weltze": {
      "type": "remote",
      "url": "https://weltze.it/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add it-weltze-weltze --url 'https://weltze.it/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  it-weltze-weltze:
    url: "https://weltze.it/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "it-weltze-weltze": {
      "Transport": "http",
      "Url": "https://weltze.it/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add it-weltze-weltze -t streamable-http -u 'https://weltze.it/mcp'
```

### Other

```json
{
  "mcpServers": {
    "it-weltze-weltze": {
      "type": "http",
      "url": "https://weltze.it/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 65, +1)

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

### 2026-11-18 (score 64, +1)

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

### 2026-11-16 (score 63, +1)

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

### 2026-11-15 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-14 (score 62)

First indexed and scored.

## MCP tools (4)

### `get_time` (~139 tokens)

Uhrzeit eines Ortes

Current local time, UTC offset, DST status and the next clock change for a place or time zone. Uses the latest IANA tz data (more current than most runtimes). Accepts city names in German or English, time zone names ("Central Time", "MEZ") or IANA IDs.

Input parameters:

- `at` (string): Optional ISO 8601 instant with offset, e.g. "2026-12-01T12:00:00Z". Default: now.
- `zone` (string, required): Place, time zone name or IANA ID, e.g. "San Diego", "Central Time", "Europe/Berlin".

### `time_difference` (~98 tokens)

Zeitverschiebung

Time difference between two places now, and how it changes over the coming months because of clock changes.

Input parameters:

- `at` (string): Optional ISO 8601 instant. Default: now.
- `from` (string, required): Reference place or zone, e.g. "Berlin".
- `months` (integer): How many months of changes to list. Default 12.
- `to` (string, required): Other place or zone, e.g. "New York".

### `convert_time` (~121 tokens)

Uhrzeit umrechnen

Convert a local wall-clock time in one place to another place. Reports nonexistent (DST gap) and ambiguous (DST overlap) times.

Input parameters:

- `disambiguation` (string): Which instant to use for an ambiguous time. Default earlier.
- `from` (string, required): Place or zone of the given time.
- `time` (string, required): Local time without offset in the "from" place, "YYYY-MM-DDTHH:MM", e.g. "2026-12-01T13:30".
- `to` (string, required): Target place or zone.

### `search_places` (~69 tokens)

Orte suchen

Search about 6,400 cities, regions, time zone names and abbreviations; returns names, countries and IANA time zones.

Input parameters:

- `limit` (integer): Default 10.
- `q` (string, required): Search text, e.g. "san diego", "central time", "IST".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/it-weltze-weltze/weltze#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62

## Common questions

### What is the weltze.it Zeitzonen MCP server?

weltze.it Zeitzonen is an MCP server listed in the public MCP registry as it.weltze/weltze. Current time, time differences, DST changes and time conversion for any city or IANA time zone. This page covers its hosted endpoint (https://weltze.it/mcp).

### Is the weltze.it Zeitzonen MCP server safe to use?

weltze.it Zeitzonen scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the weltze.it Zeitzonen MCP server expose?

weltze.it Zeitzonen exposes 4 tools: get_time, time_difference, convert_time, search_places. Their descriptions and schemas cost roughly 427 tokens of context every time the server is loaded.

### Does the weltze.it Zeitzonen MCP server require authentication?

No. We connected to weltze.it Zeitzonen without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the weltze.it Zeitzonen MCP server still maintained?

weltze.it Zeitzonen is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the weltze.it Zeitzonen MCP server?

VerifyMCP ran 12 checks on weltze.it Zeitzonen, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about weltze.it Zeitzonen: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://weltze.it/mcp
- Website: https://weltze.it/api#mcp
- Changelog RSS feed: https://verifymcp.io/servers/it-weltze-weltze/weltze.xml
- Changelog JSON feed: https://verifymcp.io/servers/it-weltze-weltze/weltze/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/it-weltze-weltze/weltze.json
- HTML version of this page: https://verifymcp.io/servers/it-weltze-weltze/weltze
