Repository navigation
error with mcp-server-time #1501
Description
When I start the mcp-server-time hair service
uvx mcpo --port 8000 -- uvx mcp-server-time --local-timezone=America/New_York
report an error.
time uvx mcpo --port 8000 -- uvx mcp-server-time --local-timezone=America/New_York Starting MCP OpenAPI Proxy on 0.0.0.0:8000 with command: uvx mcp-server-time --local-timezone=America/New_York INFO: Started server process [109656]. INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit) INFO: 222.171.7.93:27933 - “GET / HTTP/1.1” 404 Not Found INFO: 222.171.7.93:27933 - “GET / HTTP/1.1” 404 Not Found INFO: 222.171.7.93:29194 - “GET / HTTP/1.1” 404 Not Found INFO: 222.171.7.93:29194 - “GET / HTTP/1.1” 404 Not Found
Activity
maxonxie commentedon Apr 20, 2025
On MacOS command will hang long time;
uvx mcp-server-time --local-timezone=Asia/Shanghaianythingoah commentedon Aug 18, 2026
Hey, saw your issue with mcp-server-time, what tipped you off that something was wrong before you dug into the error itself?
cliffhall commentedon Oct 19, 2026
Closing: superseded by the v2 release.
Thank you for reporting this, and apologies for the long wait for a response.
Since this was filed, the reference servers have been rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers). Each server now runs on v2 of its SDK, and the behavior described here has either been fixed or no longer exists in the same form. A setup report against a pre-refactor release: the GET / 404s are normal for the mcpo proxy and a stdio server waits for a client, so no defect was identified in current code.
This is not a judgment on whether the problem was real; it's a consequence of the code it describes having been replaced. This is happening as part of the backlog triage in #4875.
If this still happens on the v2 release, we'd genuinely like to know. Please open a fresh issue with the version you're running and steps to reproduce, and we'll look at it. Note that this repository accepts contributions as issues rather than pull requests; see
CONTRIBUTING.md.Thanks for taking the time to report it.