pro.worldclock/time
REMOTE · WORLDCLOCK.PRO · SCANNED AUG 3
A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb.
Available components
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 →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 519 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · worldclock.pro
claude mcp add --transport http pro-worldclock-time https://worldclock.pro/mcp
[mcp_servers.pro-worldclock-time] url = "https://worldclock.pro/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pro-worldclock-time": {
"type": "remote",
"url": "https://worldclock.pro/mcp",
"enabled": true
}
}
} openclaw mcp add pro-worldclock-time --url https://worldclock.pro/mcp --transport streamable-http
mcp_servers:
pro-worldclock-time:
url: "https://worldclock.pro/mcp" {
"mcpServers": {
"pro-worldclock-time": {
"type": "http",
"url": "https://worldclock.pro/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 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.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 67
First indexed and scored.
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 3 Aug 2026 · Probed https://worldclock.pro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=worldclock.pro | CN=WE1,O=Google Trust Services,C=US | 13 Jul 2026 | 11 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | fbfd02ac700a44d1139016efe344b32f |
| SANs: worldclock.pro, *.worldclock.pro | ||||||
| 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 |
DNSSEC secure
Validation of worldclock.pro. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 42154 | 8 | Verified |
| worldclock.pro. | present | 2371 | 13 | Verified |
| worldclock.pro. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(self), camera=(), microphone=(), browsing-topics=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://worldclock.pro/mcp | Verified | 200 | |
| http (plaintext) | http://worldclock.pro/mcp | HTTPS enforced | 301 | https://worldclock.pro/mcp |
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.
convert_time Convert a time across locations ~109
Given a UTC instant (or a wall time in a source location), return the corresponding local time in each of up to 50 target locations. Results include a source_url linking the matching worldclock.pro page when available.
| Name | Type | Req | Description |
|---|---|---|---|
| from | object | — | Alternative to `utc`: a wall time in a specific source location. |
| targets | array | yes | — |
| utc | string | — | The instant to convert, as an ISO 8601 string. Read as UTC if it has no zone designator. |
No output schema declared.
No examples provided.
get_current_time Get current time ~101
Get the current local time (or the time at a given instant) in one or more locations. Each location is a city name, an IANA timezone / abbreviation, or coordinates. Up to 50 locations. Results include a source_url linking the matching worldclock.pro page when available.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | — | Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone). |
| locations | array | yes | — |
No output schema declared.
No examples provided.
get_dst_transitions Get DST transitions ~106
Report whether a location observes daylight saving time, the next clock change, and every summer/winter-time transition (date, local time, and before/after offset) within a year. The result includes a source_url linking the matching worldclock.pro page when available.
| Name | Type | Req | Description |
|---|---|---|---|
| location | object | yes | A location identified by exactly ONE of: query, timezone, or latitude+longitude together. |
| year | integer | — | Calendar year to list transitions for (default: the current year). |
No output schema declared.
No examples provided.
search_cities Search cities ~115
Find cities by name (multilingual, diacritic-insensitive) — useful to resolve a place to a canonical slug, IANA timezone, and coordinates before calling the time tools. Each result includes a source_url linking the city's worldclock.pro page.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | Optional ISO 3166-1 alpha-2 country filter, e.g. "JP". |
| limit | integer | — | Max results (default 10). |
| query | string | yes | City name or partial name (≥ 2 characters). |
No output schema declared.
No examples provided.
time_by_coordinates Get time by coordinates ~88
Resolve the timezone for a latitude/longitude coordinate (via geo-tz) and return the local time there.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | — | Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone). |
| latitude | number | yes | Latitude in degrees [-90, 90]. |
| longitude | number | yes | Longitude in degrees [-180, 180]. |
No output schema declared.
No examples provided.