time
Server Details
A real clock for AI agents: current time, timezone conversion, and DST facts from the IANA tzdb.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- worldclockpro/worldclock-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
5 toolsconvert_timeConvert a time across locationsRead-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| utc | No | The instant to convert, as an ISO 8601 string. Read as UTC if it has no zone designator. | |
| from | No | Alternative to `utc`: a wall time in a specific source location. | |
| targets | Yes |
get_current_timeGet current timeRead-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| at | No | Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone). | |
| locations | Yes |
get_dst_transitionsGet DST transitionsRead-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| year | No | Calendar year to list transitions for (default: the current year). | |
| location | Yes | A location identified by exactly ONE of: query, timezone, or latitude+longitude together. |
search_citiesSearch citiesRead-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10). | |
| query | Yes | City name or partial name (≥ 2 characters). | |
| country | No | Optional ISO 3166-1 alpha-2 country filter, e.g. "JP". |
time_by_coordinatesGet time by coordinatesRead-onlyIdempotentInspect
Resolve the timezone for a latitude/longitude coordinate (via geo-tz) and return the local time there.
| Name | Required | Description | Default |
|---|---|---|---|
| at | No | Optional ISO 8601 instant to evaluate instead of now (read as UTC if it has no zone). | |
| latitude | Yes | Latitude in degrees [-90, 90]. | |
| longitude | Yes | Longitude in degrees [-180, 180]. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!