Bug: Inconsistent MCP configuration behavior

Issue details

I think I stumbled upon two configuration bugs:

• When an MCP server is using an http:// URL without a port (e.g., http://localhost/mcp), fx treats that as an invalid URL instead defaulting to port 80.
• When user-profile configuration contains an "invalid" MCP server entry, the entire user-profile configuration is rejected. (In contrast, project-level configuration will skip the invalid entry, and still connect to the other MCP servers.)

So, for example, the following user-profile configuration will connect to neither MCP server:

{
  "mcp": {
    "remote-server": {
      "type": "http",
      "url": "https://mcp.example.com/mcp"
    },
    "local-server": {
      "type": "http",
      "url": "http://localhost/mcp"
    }
  }
}

Trace

No response

Sensitive information

• I reviewed the information above and removed secrets and other sensitive data.