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 by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 7.3% over 61 days
Last Tested: 2026-10-19 00:50
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: mcpcentral-io/mcp-time
GitHub Stars: 2
Server Listing: MCP Time Server

TDQS

A3.8/5.0

Scored 2026-10-15 05:15 across 6 tools

Disambiguation4/5

Each tool targets a distinct operation: timezone conversion, current time, calendar lookup, timestamp conversion, week numbering, and relative time. There is minor conceptual overlap around 'now' (current_time, relative_time) and time conversion (convert_time, get_timestamp), but descriptions make boundaries clear enough.

Naming Consistency3/5

Names mix verb_noun forms (convert_time, get_timestamp, get_week_year) with bare noun phrases (current_time, relative_time, days_in_month). Still readable and mostly snake_case, but no single predictable pattern across the set.

Tool Count5/5

Six tools is well-scoped for a focused time utility server, and each tool earns its place by covering a distinct time operation.

Completeness4/5

Core time operations are covered (conversion, current time, relative time, calendar facts). Minor gaps exist: timestamp conversion is one-directional (no timestamp-to-datetime) and there is no date arithmetic (add/subtract durations).

Available Tools

6 tools

convert_timeConvert TimezoneA

Read-onlyIdempotent

Inspect

Converts a time from a source IANA timezone to a target IANA timezone.

ParametersJSON Schema

Name	Required	Description
`time`	Yes	The time to convert (e.g., "2025-03-23 12:30:00")
`sourceTimezone`	Yes	Source IANA timezone name (e.g., "Asia/Shanghai")
`targetTimezone`	Yes	Target IANA timezone name (e.g., "Europe/London")

Output Schema

ParametersJSON Schema

Name	Required	Description
`convertedTime`	Yes
`hourDifference`	Yes

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the IANA timezone detail, which is useful. However, it does not disclose edge-case behaviors (e.g., invalid timezones, DST handling) beyond what the schema and annotations provide. With annotations present, a score of 3 is appropriate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence with no redundant information. Every word contributes to the meaning, and it is front-loaded with the core operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity, the presence of a complete output schema, and thorough annotations, the description is sufficiently complete. It correctly identifies the operation without needing to cover return values or error cases, which are handled elsewhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% — every parameter has a description with examples. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool's verb ('converts'), resource ('a time'), and scope ('from a source IANA timezone to a target IANA timezone'). It clearly distinguishes this from sibling tools like current_time or relative_time, which serve different time-related purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a clear usage context: use this tool when you need to convert a time between two IANA timezones. It does not explicitly mention alternatives or exclusions, but the clarity of the purpose makes it easy for an agent to select the tool appropriately. A slight deduction for lacking explicit contrast with sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

current_timeGet Current TimeB

Read-onlyIdempotent

Inspect

Returns the current time in UTC and a specified or guessed IANA timezone.

ParametersJSON Schema

Name	Required	Description	Default
`format`	No	Format for the returned time string (default YYYY-MM-DD HH:mm:ss)
`timezone`	No	IANA timezone name (e.g., "America/New_York"). Defaults to the server's guessed timezone

Output Schema

ParametersJSON Schema

Name	Required	Description
`utcTime`	Yes
`timezone`	Yes
`localTime`	Yes

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations (readOnlyHint=true, idempotentHint=true) already disclose safety and side-effect profiles. The description adds context that the time is returned in UTC and the IANA timezone can be specified or guessed. However, it does not elaborate on behavior such as error handling, default format, or the fact that repeated calls yield different times, leaving some transparency gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that immediately states the tool's core function. It is front-loaded and contains no filler or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, and the output schema likely covers return values, but the description lacks usage guidance and sibling differentiation. The absence of any mention of alternatives like get_timestamp creates a completeness gap, though the tool itself is well-scoped.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds little beyond the schema, only weakly referencing the timezone parameter ('specified or guessed'). It does not enrich the meaning of the 'format' parameter, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns the current time in UTC and an IANA timezone. It uses a specific verb ('Returns') and identifies the resource ('current time'). However, it does not explicitly distinguish itself from sibling tools like get_timestamp, which might also return the current time in a different format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It only states what it does, without mentioning exclusions, prerequisites, or sibling tools. For example, an agent may not know whether to choose current_time or get_timestamp for a given task.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

days_in_monthGet Days in MonthA

Read-onlyIdempotent

Inspect

Returns the number of days in the month of a given date.

ParametersJSON Schema

Name	Required	Description	Default
`date`	No	The date to check (format: YYYY-MM-DD). Defaults to current date

Output Schema

ParametersJSON Schema

Name	Required	Description
`days`	Yes

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate read-only and idempotent behavior, so the agent knows it is safe. The description adds no additional behavioral details such as leap-year handling or timezone dependence, but it also introduces no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence that gets straight to the point with no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter, strong annotations, and an output schema. The description adequately identifies the purpose while the schema handles parameter details; no critical information appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention the 'date' parameter; however, the input schema fully covers it with format and default value. With 100% schema coverage, the description need not add parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (returns) and the resource (number of days in a month for a given date). This distinguishes it from sibling tools like relative_time or get_timestamp, which serve different time/date purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit guidance on when to choose this tool over alternatives (e.g., current_time or convert_time). Usage is implied by the function—needing days in a month—but no alternatives or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_timestampGet Unix TimestampA

Read-onlyIdempotent

Inspect

Converts a date-time string to a Unix timestamp in milliseconds.

ParametersJSON Schema

Name	Required	Description	Default
`time`	No	The time to convert (format: YYYY-MM-DD HH:mm:ss). Defaults to current time

Output Schema

ParametersJSON Schema

Name	Required	Description
`timestamp`	Yes

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description aligns by describing a pure conversion operation. It adds useful context about the output unit (milliseconds) and input format, going beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no unnecessary words. It conveys the essential information efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter, full schema coverage, an output schema, and annotations covering safety. The description, combined with structured data, fully specifies behavior without missing critical details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides complete documentation for the sole parameter 'time', including format and default behavior. The tool description adds no additional parameter semantics beyond what the schema already covers, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb 'converts' and resource 'date-time string to a Unix timestamp in milliseconds', clearly distinguishing it from sibling tools like current_time (retrieves current time) and relative_time (calculates relative times).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies use for converting date-time strings to Unix timestamps, but does not explicitly mention when to avoid this tool or name alternatives such as convert_time. This is clear context without exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_week_yearGet Week of YearA

Read-onlyIdempotent

Inspect

Returns the week number and ISO week number for a given date.

ParametersJSON Schema

Name	Required	Description	Default
`date`	No	The date to check (e.g., "2025-03-23"). Defaults to current date

Output Schema

ParametersJSON Schema

Name	Required	Description
`week`	Yes
`isoWeek`	Yes

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare read-only and idempotent behavior, and the description adds clarity that both the standard week number and ISO week number are returned. No destructive side effects or auth requirements apply. The description doesn't discuss edge cases like invalid dates, but given the simplicity, this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, directly states the core functionality, and avoids redundant content. It is front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and an output schema, the description is adequate. It explains what is returned and the input is given via schema. However, it could mention the default date behavior in the description itself, but schema covers it, so minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully documents the single parameter 'date' with an example and default. The description adds no additional parameter semantics beyond saying 'for a given date', which is already evident. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns week number and ISO week number for a given date. This is specific and distinct from sibling tools like current_time or convert_time. The verb 'Returns' is functionally clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage via its statement, but there is no mention of when to choose this over relative_time or get_timestamp. Score 3 due to implied usage only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

relative_timeGet Relative TimeA

Read-onlyIdempotent

Inspect

Calculates the relative time from now to a given date-time string.

ParametersJSON Schema

Name	Required	Description	Default
`time`	Yes	The time to compare (format: YYYY-MM-DD HH:mm:ss)

Output Schema

ParametersJSON Schema

Name	Required	Description
`relativeTime`	Yes

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations (readOnlyHint: true, idempotentHint: true) already disclose the safe read-only behavior. The description adds that it computes relative time from now, but it does not provide deeper behavioral context such as timezone handling, date parsing details, or the exact nature of the output. This is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded with the action and resource. It wastes no words and is appropriately sized for a simple tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with an output schema present, the description is sufficient. It explains the core function and the input format. It does not add extra contextual details like result examples or edge cases, but these are not needed given the simplicity and output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with a clear description of the 'time' parameter including format. The description does not add meaning beyond the schema, which already fully documents the parameter. Baseline 3 is appropriate when the schema handles parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Calculates the relative time from now to a given date-time string.' The verb 'calculates' and the resource 'relative time' are specific, and this tool is distinguishable from siblings like current_time or get_timestamp by focusing on relative time.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool (when you need relative time from now to a given date), but it does not explicitly contrast with alternatives or provide exclusions. The tool's purpose alone suggests usage, but there is no direct 'use this when...' or mention of sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

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

Related MCP Connectors

Timeapi Io B
io.github.pipeworx-io
TimeAPI.io MCP.
Location Services Developer Tools
2
TimesheetOAuth
io.github.timesheetIO
timesheet.io MCP server - manage timers, projects, tasks and reports
Project Management Workplace & Productivity
11
cloudtime API
io.github.julysoft
MCP server providing attendance data queries via the CloudTime API.
Workplace & Productivity
2
Timezone A
io.github.pipeworx-io
Timezone MCP — wraps timeapi.io (free, no auth)
Location Services Search
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 3 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 8 months ago (2026-02-18 10:34 UTC)
2
30 PyPI
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 10 months ago (2025-12-27 03:53 UTC)
-

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources