A
licenseB
qualityD
maintenanceProvides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.
2
MIT
MCP-timeserver
The MCP-timeserver provides datetime information to systems and tools.
Access time in specific timezones: Using the
datetime://URI scheme (e.g.,datetime://Europe/London/now)Retrieve current local time: Using the
get_current_time()tool, which returns the time in the system's configured timezone
Allows accessing current date/time information through a datetime:// URI scheme with '/now' endpoint
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP-timeserverwhat time is it in Tokyo right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP-timeserver
A simple MCP server that exposes datetime information to agentic systems and chat REPLs
Components
Resources
The server implements a simple datetime:// URI scheme for accessing the current date/time in a given timezone, for example:
datetime://Africa/Freetown/now
datetime://Europe/London/now
datetime://America/New_York/nowTools
The server exposes a tool to get the current local time in the system timezone:
>>> get_current_time()
"The current time is 2024-12-18 19:59:36"Related MCP server: Timezone MCP Server
Quickstart
Install
use the following json
{
"mcpServers": {
"MCP-timeserver": {
"command": "uvx",
"args": ["MCP-timeserver"]
}
}
}Available Tools
1 toolget-current-timeA
Get the current time in the configured local timezone
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the behavioral trait of returning time in a 'configured local timezone', which adds context beyond a basic time query. However, it doesn't mention potential issues like timezone configuration errors, response format, or latency.
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, efficient sentence with no wasted words. It is front-loaded with the core purpose and includes necessary context ('configured local timezone') without redundancy.
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?
Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It specifies the timezone aspect, which is crucial for understanding the output. However, without an output schema, it could briefly hint at the return format (e.g., timestamp string) for better completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description adds no parameter-specific information, but this is acceptable given the baseline of 4 for zero-parameter tools, as it doesn't need to compensate for gaps.
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 specific action ('Get') and resource ('current time'), with precise scope ('in the configured local timezone'). It distinguishes itself by specifying the timezone context, though no sibling tools exist for comparison.
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 usage for retrieving the current time in a specific timezone, but provides no explicit guidance on when to use this tool versus alternatives (e.g., UTC time tools) or any prerequisites. With no sibling tools, the baseline is adequate but lacks proactive guidance.
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. Dates show when Glama detected each change.
1 tool update
- First observed
get-current-time
TDQS
A3.9/5.0
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clear, so an agent cannot misselect between non-existent alternatives.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern (get-current-time), and with no other tools to compare, there is no inconsistency. The naming is straightforward and predictable.
Tool Count2/5
A single tool for a time server feels thin and under-scoped, as it only provides current time retrieval without obvious related operations like time conversion, formatting, or scheduling. This minimal set may limit functionality for typical time-related tasks.
Completeness2/5
The tool surface is severely incomplete for a time server domain, lacking basic operations such as converting between timezones, formatting times, or handling dates. It covers only a narrow slice of potential time-related functionality, likely causing agent failures in broader scenarios.
Maintenance
ActivityInactive
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Get the current time anywhere and access concise timezone information. Set your preferred timezone…
Get the current time in any timezone and quickly look up common timezone info. Set a default timez…
Get the current time in your chosen timezone and view common timezone information. Simplify schedu…
Get the current time in any timezone. Explore concise timezone info to pick the right region. Simp…
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to get current time information for any timezone worldwide, including available regions, cities, and ISO 8601 formatted timestamps with timezone offsets.8-
- AlicenseNot gradedqualityCmaintenanceProvides time zone management utilities including retrieving current time in any global time zone and converting time between different time zones with automatic daylight saving time handling.73MIT
- FlicenseBqualityDmaintenanceProvides current time and timezone conversion using IANA timezone names, with automatic system timezone detection.2-
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SecretiveShell/MCP-timeserver'
If you have feedback or need assistance with the MCP directory API, please join our Discord server