It seems that goose does not handle the relative endpoint URI correctly.

When I attempt to discover an MCP SSE endpoint in a quarkus-mcp-server app (https://github.com/quarkiverse/quarkus-mcp-server/tree/main/samples/weather) the CLI reports an invalid POST endpoint URI:

Discovered SSE POST endpoint: http://localhost:8080/mcp/mcp/messages/Nzc5YTg5MjUtZDA0Yy00YzEyLTkwODUtZDM4MGRkNmY5YmQw

Note that the server returned the endpoint URI /mcp/messages/Nzc5YTg5MjUtZDA0Yy00YzEyLTkwODUtZDM4MGRkNmY5YmQw and the base URI (SSE endpoint) is http://localhost:8080/mcp/sse so I would expect the POST endpoint http://localhost:8080/mcp/messages/Nzc5YTg5MjUtZDA0Yy00YzEyLTkwODUtZDM4MGRkNmY5YmQw.

Am I missing something?