mcp-time
Server Details
Time MCP server via HTTP
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- mcpcentral-io/mcp-time
- GitHub Stars
- 2
- Server Listing
- MCP Time Server
TDQS
Scored across 6 tools
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.
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.
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.
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
6 tool updates
- Changed
convert_time7 fields changed- added
Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#" - added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / sourceTimezone / descriptionPrevious value: -"The source IANA timezone name (e.g., \"Asia/Shanghai\")."New value: +"Source IANA timezone name (e.g., \"Asia/Shanghai\")" - changed
Input schema / properties / targetTimezone / descriptionPrevious value: -"The target IANA timezone name (e.g., \"Europe/London\")."New value: +"Target IANA timezone name (e.g., \"Europe/London\")" - changed
Input schema / properties / time / descriptionPrevious 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\")" - changed
Input schema / requiredPrevious value: -[ - "sourceTimezone", - "targetTimezone", - "time" -]New value: +[ + "time", + "sourceTimezone", + "targetTimezone" +] - changed
Output 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" +}
- Changed
current_time6 fields changed- added
Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#" - added
Input schema / additionalPropertiesAdded value: +false - removed
Input schema / properties / format / defaultRemoved value: -"YYYY-MM-DD HH:mm:ss" - changed
Input schema / properties / format / descriptionPrevious value: -"The format for the returned time string."New value: +"Format for the returned time string (default YYYY-MM-DD HH:mm:ss)" - changed
Input schema / properties / timezone / descriptionPrevious 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" - changed
Output 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" +}
- Changed
days_in_month4 fields changed- added
Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#" - added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / date / descriptionPrevious value: -"The date to check. Format: YYYY-MM-DD"New value: +"The date to check (format: YYYY-MM-DD). Defaults to current date" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "days": { + "type": "integer" + } + }, + "required": [ + "days" + ], + "type": "object" +}
- Changed
get_timestamp4 fields changed- added
Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#" - added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / time / descriptionPrevious 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" - changed
Output schema / (root)Previous value: -nullNew value: +{ + "$schema": "http://json-schema.org/draft-07/schema#", + "additionalProperties": false, + "properties": { + "timestamp": { + "type": "number" + } + }, + "required": [ + "timestamp" + ], + "type": "object" +}
- Changed
get_week_year4 fields changed- added
Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#" - added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / date / descriptionPrevious 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" - changed
Output 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" +}
- Changed
relative_time4 fields changed- added
Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#" - added
Input schema / additionalPropertiesAdded value: +false - changed
Input schema / properties / time / descriptionPrevious 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)" - changed
Output 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 updates
- First observed
convert_time - First observed
current_time - First observed
days_in_month - First observed
get_timestamp - First observed
get_week_year - First observed
relative_time
Related MCP Connectors
timesheet.io MCP server - manage timers, projects, tasks and reports
MCP server providing attendance data queries via the CloudTime API.
Timezone MCP — wraps timeapi.io (free, no auth)
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceMCP server providing time retrieval and echo tools, running as an independent network process over Streamable HTTP.-
- AlicenseAqualityCmaintenanceAn MCP server that allows checking local time on the client machine or current UTC time from an NTP server234MIT
- AlicenseBqualityDmaintenanceA lightweight mcp server that tells you exactly what time is it based on your IP.19MIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that provides current time information with configurable timezone support set on the client side.-
Glama MCP Gateway
Add one secure layer between your agents and this server.