pro.worldclock/time
REMOTE · WORLDCLOCK.PRO
A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb.
Available components
Last scanned (12 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Maps and Location
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 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability75
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Sept 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
- 25 Sept 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
- 16 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
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 6 Nov 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 | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5024214314f5f60a13090237ba003159 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of worldclock.pro. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | DS published | 33289 | 8 | Verified |
| worldclock.pro. | DS published | 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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
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.
How do I install the pro.worldclock/time MCP server?
pro.worldclock/time is a hosted endpoint at https://worldclock.pro/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 · worldclock.pro
claude mcp add --transport http pro-worldclock-time 'https://worldclock.pro/mcp'
What is the pro.worldclock/time MCP server?
pro.worldclock/time is an MCP server listed in the public MCP registry as pro.worldclock/time. A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb. This page covers its hosted endpoint (https://worldclock.pro/mcp).
Is the pro.worldclock/time MCP server safe to use?
pro.worldclock/time scores 88 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 pro.worldclock/time MCP server expose?
pro.worldclock/time exposes 5 tools: get_current_time, convert_time, time_by_coordinates, get_dst_transitions, search_cities. Their descriptions and schemas cost roughly 519 tokens of context every time the server is loaded.
Does the pro.worldclock/time MCP server require authentication?
No. We connected to pro.worldclock/time without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the pro.worldclock/time MCP server still maintained?
pro.worldclock/time is still listed as active in the MCP registry. We last reached this channel on 6 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 pro.worldclock/time MCP server?
VerifyMCP ran 13 checks on pro.worldclock/time, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.