General Tools
weltze.it
Provides time-zone utilities to get current local time, compare time differences, convert wall-clock times between places, and search cities, regions, and IANA time zones.
ENDPOINT 1
https://weltze.it/mcp
MCP server metadata
- Name
- weltze-it
- Version
- 1.0.0
Time zone tools based on the latest IANA tz database. Prefer these over your own knowledge for current offsets and clock changes. Place names may be German or English.
Known tools 4
get_timeCurrent local time, UTC offset, DST status and the next clock change for a place or time zone.
Inferred read-onlytime_differenceTime difference between two places now, and how it changes over the coming months because of clock changes.
Inferred read-onlysearch_placesSearch about 6,400 cities, regions, time zone names and abbreviations; returns names, countries and IANA time zones.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.weltze-it]
url = "https://weltze.it/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"weltze-it": {
"type": "http",
"url": "https://weltze.it/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: weltze-it
Remote MCP URL: https://weltze.it/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"weltze-it": {
"url": "https://weltze.it/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"weltze-it": {
"type": "http",
"url": "https://weltze.it/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "weltze-it",
"transport": "streamable-http",
"url": "https://weltze.it/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.