A
licenseB
qualityD
maintenanceA lightweight mcp server that tells you exactly what time is it based on your IP.
1
9
MIT
MCP Simple Timeserver
by andybrandt
MCP Einfacher Zeitserver
Eine der seltsamen Designentscheidungen von Anthropic bestand darin, Claude die Zeitstempel für vom Benutzer gesendete Nachrichten und die aktuelle Uhrzeit generell vorzuenthalten. Der arme Claude kann nicht sagen, wie spät es ist! mcp-simple-timeserver ist ein einfacher MCP-Server, der dieses Problem behebt.
Dieser Server bietet zwei Tools:
get_timeliefert die aktuelle Ortszeit und Zeitzone des Benutzerrechners. So kann Claude die aktuelle Uhrzeit am Standort des Benutzers ermitteln. Bei Bedarf kann er auch die Zeit seit seiner letzten Interaktion mit dem Benutzer berechnen.get_utcliefert die aktuelle UTC-Zeit, die von einem NTP-Zeitserver abgerufen wurde.
Installation
Installation über Smithery
So installieren Sie Simple Timeserver für Claude Desktop automatisch über Smithery :
npx -y @smithery/cli install mcp-simple-timeserver --client claudeManuelle Installation
Installieren Sie zunächst das Modul mit:
pip install mcp-simple-timeserver
Konfigurieren Sie es dann im MCP-Client – der Claude-Desktop-App .
Unter Mac OS sieht dies folgendermaßen aus:
"mcpServers": {
"simple-timeserver": {
"command": "python",
"args": ["-m", "mcp_simple_timeserver"]
}
}Unter Windows müssen Sie den Pfad zu Ihrer ausführbaren Python-Datei überprüfen, indem Sie in der cmd (Windows-Befehlszeile) „ where python verwenden.
Eine typische Konfiguration würde folgendermaßen aussehen:
"mcpServers": {
"simple-timeserver": {
"command": "C:\\Users\\YOUR_USERNAME\\AppData\\Local\\Programs\\Python\\Python311\\python.exe",
"args": ["-m", "mcp_simple_timeserver"]
}
}Available Tools
2 toolsget_local_timeGet Local Time and TimezoneARead-only
Returns the current local time and timezone information from your local machine. This helps you understand what time it is for the user you're assisting.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds value by specifying that the data comes from 'your local machine' and its purpose for assisting users, which provides useful context beyond the annotations. However, it does not disclose additional behavioral traits like performance or error handling.
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 two sentences, front-loaded with the core functionality and followed by a brief explanation of its utility. Every sentence adds value without redundancy, making it efficient and well-structured.
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 low complexity (0 parameters, read-only, with output schema), the description is complete enough for its purpose. It explains what the tool returns and why it's useful, and with an output schema present, it does not need to detail return values. However, it could be more explicit about sibling differentiation.
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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not mention parameters, which is appropriate. Baseline is 4 for zero parameters, as the description does not need to compensate for any gaps.
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 the tool's purpose with a specific verb ('Returns') and resource ('current local time and timezone information from your local machine'). It distinguishes from the sibling 'get_utc' by specifying 'local' time, though not explicitly naming the alternative. The description avoids tautology by explaining what the tool does rather than restating the name.
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 context by stating 'This helps you understand what time it is for the user you're assisting,' which suggests when to use it. However, it does not explicitly state when to use this tool versus the sibling 'get_utc' or provide any exclusions. The guidance is present but not comprehensive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_utcGet UTC Time from an NTP ServerARead-only
Returns accurate UTC time from an NTP server. This provides a universal time reference regardless of local timezone.
:param server: NTP server address (default: pool.ntp.org)
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| server | No | pool.ntp.org |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds useful context about accuracy ('accurate UTC time') and the universal time reference aspect, though it doesn't mention potential network dependencies or rate limits.
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 efficiently structured with three sentences that each add value: stating the core function, explaining the benefit, and clarifying the parameter. No wasted words.
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 (one optional parameter), presence of readOnlyHint annotation, and existence of an output schema, the description provides complete context for effective use without needing to explain return values.
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?
With 0% schema description coverage, the description compensates by explaining the 'server' parameter's purpose ('NTP server address') and default value, adding meaningful semantics beyond the bare schema.
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 ('Returns accurate UTC time') and resource ('from an NTP server'), distinguishing it from the sibling tool 'get_local_time' by emphasizing universal time reference regardless of local timezone.
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 provides clear context for when to use this tool ('provides a universal time reference regardless of local timezone'), which implicitly differentiates it from 'get_local_time', but doesn't explicitly state when not to use it or name alternatives.
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.
2 tool updates
v1.0.0- Changed
get_local_time2 fields changed- removed
Output schema / properties / result / titleRemoved value: -"Result" - removed
Output schema / titleRemoved value: -"_WrappedResult"
- Changed
get_utc3 fields changed- removed
Input schema / properties / server / titleRemoved value: -"Server" - removed
Output schema / properties / result / titleRemoved value: -"Result" - removed
Output schema / titleRemoved value: -"_WrappedResult"
2 tool updates
- First observed
get_local_time - First observed
get_utc
TDQS
A3.9/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: get_local_time provides local time with timezone information, while get_utc provides universal time from an NTP server. There is no overlap or ambiguity between these functions.
Naming Consistency5/5
Both tools follow a consistent verb_noun naming pattern (get_local_time, get_utc) with the same verb 'get' and clear noun objects. The naming is perfectly uniform and predictable.
Tool Count3/5
With only 2 tools, the server feels somewhat thin for a timeserver domain. While the tools cover basic time retrieval, additional functionality like time conversion, formatting, or scheduling might be expected but is missing.
Completeness3/5
The server provides core time retrieval functions (local and UTC), but lacks operations for time manipulation, conversion between timezones, or date calculations. These gaps limit the server's utility for more complex time-related tasks.
Maintenance
ActivityInactive
ResponsivenessResponsive
Related MCP Connectors
MCP server providing attendance data queries via the CloudTime API.
Related MCP Servers
- FlicenseBqualityDmaintenanceA simple MCP server that provides accurate date and time information to Claude models, ensuring they always use the correct current date and time when creating time-sensitive content.3-
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server that provides current time information with configurable timezone support set on the client side.-
- AlicenseAqualityFmaintenanceMCP server providing various date/time functions including current time, timezone conversion, and relative time calculations. Supports both local stdio and remote HTTP access via Cloudflare Workers.6300 npm2MIT