mcp-time

Name: mcp-time
Author: mcpcentral-io

Server Details

Time MCP server via HTTP

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-06 07:31
Transport: Streamable HTTP
URL
Repository: mcpcentral-io/mcp-time
GitHub Stars: 2
Server Listing: MCP Time Server

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

6 tool updatesApr 18, 2026

Changedconvert_time7 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / sourceTimezone / description

Previous value: -"The source IANA timezone name (e.g., \"Asia/Shanghai\")."New value: +"Source IANA timezone name (e.g., \"Asia/Shanghai\")"

changedInput schema / properties / targetTimezone / description

Previous value: -"The target IANA timezone name (e.g., \"Europe/London\")."New value: +"Target IANA timezone name (e.g., \"Europe/London\")"

changedInput schema / properties / time / description

Previous value: -"The time to convert. e.g., \"2025-03-23 12:30:00\"."New value: +"The time to convert (e.g., \"2025-03-23 12:30:00\")"

changedInput schema / required

Previous value: -[
-  "sourceTimezone",
-  "targetTimezone",
-  "time"
-]New value: +[
+  "time",
+  "sourceTimezone",
+  "targetTimezone"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "convertedTime": {
+      "type": "string"
+    },
+    "hourDifference": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "convertedTime",
+    "hourDifference"
+  ],
+  "type": "object"
+}

Changedcurrent_time6 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / format / default
```
Removed value: -"YYYY-MM-DD HH:mm:ss"
```

changedInput schema / properties / format / description

Previous value: -"The format for the returned time string."New value: +"Format for the returned time string (default YYYY-MM-DD HH:mm:ss)"

changedInput schema / properties / timezone / description

Previous value: -"The IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone."New value: +"IANA timezone name (e.g., \"America/New_York\"). Defaults to the server's guessed timezone"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "localTime": {
+      "type": "string"
+    },
+    "timezone": {
+      "type": "string"
+    },
+    "utcTime": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "utcTime",
+    "localTime",
+    "timezone"
+  ],
+  "type": "object"
+}

Changeddays_in_month4 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / date / description

Previous value: -"The date to check. Format: YYYY-MM-DD"New value: +"The date to check (format: YYYY-MM-DD). Defaults to current date"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "days": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "days"
+  ],
+  "type": "object"
+}

Changedget_timestamp4 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / time / description

Previous value: -"The time to convert. Format: YYYY-MM-DD HH:mm:ss"New value: +"The time to convert (format: YYYY-MM-DD HH:mm:ss). Defaults to current time"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "timestamp": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "timestamp"
+  ],
+  "type": "object"
+}

Changedget_week_year4 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / date / description

Previous value: -"The date to check. e.g., \"2025-03-23\""New value: +"The date to check (e.g., \"2025-03-23\"). Defaults to current date"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "isoWeek": {
+      "type": "integer"
+    },
+    "week": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "week",
+    "isoWeek"
+  ],
+  "type": "object"
+}

Changedrelative_time4 fields changed

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / time / description

Previous value: -"The time to compare. Format: YYYY-MM-DD HH:mm:ss"New value: +"The time to compare (format: YYYY-MM-DD HH:mm:ss)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "relativeTime": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "relativeTime"
+  ],
+  "type": "object"
+}

6 tool updatesJan 31, 2026
- First observedconvert_time
- First observedcurrent_time
- First observeddays_in_month
- First observedget_timestamp
- First observedget_week_year
- First observedrelative_time

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

cloudtime API
io.github.julysoft
MCP server providing attendance data queries via the CloudTime API.
Workplace & Productivity
2
mcp-shorturlOAuth
io.github.AceDataCloud
MCP server for URL shortening and management
App Automation
21
hostinger-api-mcpOAuth
io.github.hostinger
MCP server for Hostinger API
Cloud Platforms Developer Tools
1150
Home Automation Mcp D
io.github.varvararatta
MCP server for Home Automation
Home Automation & IoT
2

Related MCP Servers

Jarvis MCP Server
Location Services Developer Tools
AlexanderBuiko
F
license
Not graded
quality
C
maintenance
MCP server providing time retrieval and echo tools, running as an independent network process over Streamable HTTP.
Updated 2 months ago (2026-07-15 20:56 UTC)
-
MCP Simple Timeserver
OS Automation
andybrandt
A
license
A
quality
C
maintenance
An MCP server that allows checking local time on the client machine or current UTC time from an NTP server
Updated 7 months ago (2026-02-18 10:34 UTC)
2
34
MIT
whattimeisit-mcp
Location Services
kukapay
A
license
B
quality
D
maintenance
A lightweight mcp server that tells you exactly what time is it based on your IP.
Updated a year ago (2025-05-07 17:25 UTC)
1
9
MIT
MCP Time Server
Developer Tools
siberianwm
F
license
Not graded
quality
D
maintenance
A minimal MCP server that provides current time information with configurable timezone support set on the client side.
Updated 8 months ago (2025-12-27 03:53 UTC)
-

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: convert_time handles timezone conversion, current_time provides current time, days_in_month gives calendar information, get_timestamp converts to Unix time, get_week_year provides week numbering, and relative_time calculates time differences. An agent can easily distinguish between these operations.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern throughout (convert_time, current_time, days_in_month, get_timestamp, get_week_year, relative_time), with all tools using snake_case. The minor deviation is that 'relative_time' uses an adjective rather than a verb, but this is still readable and maintains overall consistency.

Tool Count5/5

With 6 tools, this is well-scoped for a time-related server. Each tool earns its place by covering distinct aspects of time operations (conversion, current time, calendar info, timestamping, week numbering, and relative calculations), avoiding both bloat and thin functionality.

Completeness4/5

The toolset covers core time operations comprehensively, including conversion, current time retrieval, calendar details, timestamping, week info, and relative time. A minor gap is the lack of date arithmetic (e.g., add/subtract days) or time formatting tools, but agents can work around this with existing tools.

Server Details

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

Jarvis MCP Server

MCP Simple Timeserver

whattimeisit-mcp

MCP Time Server

Glama MCP Gateway

TDQS

Resources