Running time mcp with streamable-http is returning unhealthy status
Open
Nobody has claimed this yet.
bug
proxy
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Bug description
Running the Time MCP with streamable-http transport, returns unhealthy status
Steps to reproduce
Run Time mcp using the streamable-http transport
Expected behavior
Explain what you expected to happen.
Actual behavior
Explain what actually happened.
Environment (if relevant)
- OS/version:
- ToolHive version:
Additional context
Logs:
Detected initialize method call for time_test_edit
1:08PM ERROR Failed to forward request: dial tcp 127.0.0.1:32621: connect: connection refused
2025/09/11 13:08:54 http: proxy error: dial tcp 127.0.0.1:32621: connect: connection refused
1:08PM ERROR Failed to forward request: dial tcp 127.0.0.1:32621: connect: connection refused
2025/09/11 13:08:54 http: proxy error: dial tcp 127.0.0.1:32621: connect: connection refused
1:08PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:09PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:09PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:09PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:09PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:09PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:09PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:10PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:10PM INFO MCP server not initialized yet, skipping health check for time_test_edit
1:10PM INFO MCP server not initialized yet, skipping health check for time_test_edit
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 Time MCP with the streamable-http transport and review the logged connection-refused errors alongside the repeated health-check messages. The issue needs a complete expected and actual behavior description; done means the server initializes successfully and reports the correct health status without these proxy errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100