[Discovery] mcp/time - Timezone Operations
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, node.js, typescript
Research direction
Start by reviewing the upstream src/time server and this repository's time.dockerfile. Check the listed timezone-support documentation and HADOLint items, then record their results; treat the proposed Rust rewrite as a separate design decision because the issue does not define its scope or acceptance criteria.
Written by the indexing model from the issue text.
Description
Project Association
This issue tracks the mcp/time MCP server in the core profile.
Server Details
- Name: time
- Source: https://github.com/modelcontextprotocol/servers/tree/main/src/time
- Docker Hub: https://hub.docker.com/r/mcp/time
- Category: global/utility
- Language: TypeScript/Node.js
Transport Status
- Current: stdio only (upstream)
- Implementation: HTTP-wrapped via supergateway
- Docker Image:
time-mcp:http(custom build)
Tools Provided
get_current_time: Get current time in a specific timezoneconvert_time: Convert time between timezones
Docker Status
- Official image:
mcp/time - Custom wrapper:
time.dockerfile(extends base with supergateway) - HADOLint: Not checked
Notes
- Simple utility server with minimal resource requirements
- Good candidate for Rust rewrite due to simplicity
Tracking
- Document timezone support
- HADOLint compliance check
- Consider Rust rewrite (high priority - simple server)
- Dominant language
- Just
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aRustyDev/mcp
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
category/docs phase/discovery transport/http-streamed type/research
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
category/workflow phase/discovery transport/http-streamed type/research
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
area/sessions comp/cron comp/gateway P2 sweeper:risk-message-delivery sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#118863 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·