Well, as the owner of AntiXSS I'd obviously say yes. However I'm biased :)
AntiXSS gives you
- More encoding options - including encoding for CSS, JavaScript and LDAP (should you be querying AD from your code)
- A safe list, rather than an unsafe list. This is inherently more secure, but is slower. Whilst the default .NET blacklist is good enough, it does depend on how your systems handle input too.
Now, with AntiXSS 4.1 you can easily get AntiXSS to plug into MVC and be used as the default encoder. That's a beta right now, the code is available for download along with limited instructions on how to swap out the encoder. You should see release within before November.