Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

weltze.it Zeitzonen

REMOTE · WELTZE.IT

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

Available components

+3 this week 65 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 463 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 15 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://weltze.it/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=weltze.it CN=WE1,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA256 5e0658a40a1b3233133ccb81ab93322a
SANs: weltze.it
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of weltze.it. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
it. DS published 51765 13 Verified
weltze.it. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://weltze.it/mcp Verified 200
http (plaintext) http://weltze.it/mcp HTTPS enforced 301 https://weltze.it/mcp
MCP tools · 4 exposed · ~427 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
convert_time ~121

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

NameTypeReqDescription
disambiguationstring–Which instant to use for an ambiguous time. Default earlier.
fromstringyesPlace or zone of the given time.
timestringyesLocal time without offset in the "from" place, "YYYY-MM-DDTHH:MM", e.g. "2026-12-01T13:30".
tostringyesTarget place or zone.

No output schema declared.

No examples provided.

get_time ~139

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.

NameTypeReqDescription
atstring–Optional ISO 8601 instant with offset, e.g. "2026-12-01T12:00:00Z". Default: now.
zonestringyesPlace, time zone name or IANA ID, e.g. "San Diego", "Central Time", "Europe/Berlin".

No output schema declared.

No examples provided.

search_places ~69

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

NameTypeReqDescription
limitinteger–Default 10.
qstringyesSearch text, e.g. "san diego", "central time", "IST".

No output schema declared.

No examples provided.

time_difference ~98

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

NameTypeReqDescription
atstring–Optional ISO 8601 instant. Default: now.
fromstringyesReference place or zone, e.g. "Berlin".
monthsinteger–How many months of changes to list. Default 12.
tostringyesOther place or zone, e.g. "New York".

No output schema declared.

No examples provided.

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.

remote · weltze.it

# add to Claude Code
claude mcp add --transport http it-weltze-weltze 'https://weltze.it/mcp'
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.