When accessing the remote MCP server at https://mcp.tavily.com/mcp/?tavilyApiKey=[api_key], the http request is returning a 307 to the same url but on http protocol (http://mcp.tavily.com/mcp/?tavilyApiKey=[api_key]), which understandably doesn’t have a listener.
I don’t see any issues on the status page
An update, this appears to be related to an additional slash in the MCP server URL. When the url used for the SSE transport is https://mcp.tavily.com/mcp/?tavilyApiKey=<api_key> - then the redirect is occurring to http://mcp.tavily.com/mcp?tavilyApiKey=<api_key>. It appears that the redirection to remove the trailing slash is also changing the protocol.
When accessing the https endpoint, without the trailing slash the redirect doesn’t occur.
Since the MCP spec and transports don’t generally include automatically following redirections (though please correct me if I’m wrong), I’d propose correcting the pathing before it hits the server at your WAF/API Gateway