I think not... ;)

I understand Ocramius points. But if on of this service will be down (and that time will come) we can ignore that because we can push the rerun button for that case we need that result. On the other hand, Scrutinizer don't support database environment. So if we build the test for that CI it never run with 100% coverage.