This class doesn't feel like it hangs together all that well. Whilst objects without behaviour have their place (at the edges of an application), an object with lots of behaviour and no state can imply a low level of cohesion, and I think that is the case here. The methods exposed by this class don't present a cohesive interface; instead it seems to be more of a dumping ground for all the methods you need in another layer of the application.