Skip to main content
Glama
fangmd

Time MCP

by fangmd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Time MCP

A Model Context Protocol (MCP) server that provides time-related tools for LLM applications.

Features

  • Get current UTC time in ISO 8601 format

  • Get Unix timestamp

  • Support for timezone queries (optional extension)

Related MCP server: Time MCP Server

Requirements

  • Node.js 18+

  • pnpm

Docker Deployment

🐳 Docker 部署: 查看 DOCKER.md 了解如何使用 Docker 和 Docker Compose 部署 Time MCP 服务器。

快速开始：

docker-compose up -d

Installation

pnpm install

Development

# Run in development mode (Stdio mode)
pnpm dev

# Run in HTTP mode (development)
pnpm dev:http

# Build for production
pnpm build

# Run production build (Stdio mode)
pnpm start

# Run production build (HTTP mode)
pnpm start:http

Transport Modes

This server supports two transport modes:

Stdio Mode (Default)

The server communicates via standard input/output streams. This is the default mode and is suitable for local process communication.

pnpm dev
# or
TRANSPORT=stdio pnpm start

HTTP Mode

The server runs as an HTTP server and can be accessed remotely. Suitable for remote deployment and network communication.

# Development
pnpm dev:http

# Production
TRANSPORT=http PORT=3000 HOST=0.0.0.0 pnpm start

Environment Variables for HTTP Mode:

  • TRANSPORT: Transport type (stdio | http), default: stdio

  • PORT: HTTP port (HTTP mode), default: 3000

  • HOST: HTTP listen address (HTTP mode), default: 0.0.0.0

  • MCP_PATH or API_PATH: HTTP API path (HTTP mode), default: /mcp

  • LOG_LEVEL: Log level (DEBUG | INFO | WARN | ERROR), default: INFO

Logging

The server includes comprehensive logging for troubleshooting. Logs are output to stderr (following MCP protocol conventions).

Log Levels:

  • DEBUG: Detailed debug information (most verbose)

  • INFO: General informational messages (default)

  • WARN: Warning messages

  • ERROR: Error messages only (least verbose)

Setting Log Level:

# Set log level via environment variable
LOG_LEVEL=DEBUG pnpm dev
LOG_LEVEL=ERROR pnpm start:http

What Gets Logged:

  • Server startup and shutdown

  • Transport creation and connection

  • HTTP request/response details (method, path, duration)

  • Tool calls (name, arguments, results)

  • Errors with stack traces

Usage

📖 详细使用文档: 查看 USAGE.md 了解如何在其他 LLM 应用中集成和使用 time-mcp，包括在 OpenAI JS SDK Response API 中的完整示例。

This MCP server provides the following tools:

getCurrentTime

Returns the current UTC time in ISO 8601 format along with Unix timestamp.

Parameters: None

Returns:

{
  "timestamp": "2024-01-01T12:00:00.000Z",
  "iso": "2024-01-01T12:00:00.000Z",
  "unix": 1704110400000
}

License

ISC

Available Tools

1 tool
getCurrentTimeA

Get the current UTC time in ISO 8601 format along with Unix timestamp

ParametersJSON Schema
NameRequiredDescriptionDefault

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 output format (ISO 8601 and Unix timestamp) but does not mention behavioral traits like rate limits, errors, or side effects. It adequately describes what it returns without extra context.

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 that front-loads the purpose with zero waste. Every word contributes directly to understanding the tool's function without unnecessary elaboration.

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 complete enough for its purpose. It specifies the output format clearly, though it could mention any limitations or assumptions, making it slightly less than fully comprehensive.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter semantics, but with no parameters, this meets the baseline of 4 for being complete in this context.

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 the resource ('current UTC time'), specifying both ISO 8601 format and Unix timestamp. It distinguishes what it provides without siblings to differentiate from, making it maximally 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?

The description implies usage for obtaining current time data but provides no explicit guidance on when to use it versus alternatives, prerequisites, or exclusions. With no siblings, this 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. 1 tool updatev1.0.0
    • First observedgetCurrentTime
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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 clearly defined.

Naming Consistency5/5

A single tool inherently has perfect naming consistency. The name 'getCurrentTime' follows a clear verb_noun pattern and is descriptive.

Tool Count2/5

One tool is too few for most server purposes, as it limits functionality and may not cover the domain adequately. For a time-related server, additional tools like time conversion, timezone handling, or scheduling might be expected.

Completeness2/5

The server is severely incomplete for a time-related domain. It only provides current time retrieval, lacking essential operations such as timezone conversions, date calculations, or formatting options, which are common in time utilities.

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

Related MCP Servers

  • Time MCP Server

    ampcome-mcps
    A
    license
    B
    quality
    D
    maintenance
    Gives large language models time awareness capabilities through various time-related functions including current time retrieval, timezone conversion, and relative time calculations.
    6
    1,823
    MIT

  • Time MCP Server

    dumyCq
    A
    license
    B
    quality
    D
    maintenance
    Provides time and timezone functionality for LLMs, enabling them to get current time information across different timezones and convert times between zones.
    2
    MIT

  • mcp-epochs

    daedalus
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides current Unix timestamp in seconds, milliseconds, and ISO 8601 format to LLMs via a simple MCP tool.
    MIT

  • Time MCP Server

    adubovik
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides current time and timezone conversion using IANA timezone names, enabling LLMs to get system time or convert times between timezones.
    MIT

Latest Blog Posts

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/fangmd/time-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server