modelcontextprotocol / modelcontextprotocol/servers
error with mcp-server-time
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
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
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.
Research direction
Start by reproducing the reported uvx mcpo --port 8000 -- uvx mcp-server-time --local-timezone=America/New_York command and inspect how the proxy handles requests to /. Compare the request path with the server's available entry points; done means determining whether the repeated 404 responses are expected or identifying the configuration or behavior that causes them.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100