See the rest of the maps: http://tiles.mapbox.com/mapbox In short, not really, but kind of. Global SRTM = a lot of preprocessing, postprocessing, and design choices, that we haven't been motivated to do by any specific use case.
"Global SRTM = a lot of preprocessing, postprocessing, and design choices" -- yes but only once per year or so. Terrain data doesn't get monthly or quarterly quality upgrades like OSM data or satellite aerials do.
For anyone interested, from my own experience a few weeks back when I hacked up my elevation data workflow in 1-2 days. First off, data sources:
1. CGIAR-CSI for SRTM3, v4.1 core elevation tiles (N60 down to S60)
2. vastly improved-over-SRTM .hgt tiles for various mountaineous areas and many north-of-N60 areas from viewfinderpanoramas.org, can replace SRTM tiles with those where applicable but they don't have global coverage so need to merge 1. and 2.
3. anything not covered by 1. and 2. use the HGT tiles by "Radio Mobile" (rmw.recordist.com)
Now encode all roughly 144*360=51840 (minus pure ocean) tiles either to GeoTiffs (insane storage space requirements!) or (my approach) to PNG using any custom mapping of the elevation signed-int16 values to your RGB(A) channels. The compression/decompression is fast yet the storage needs are awesome, some 300kb max for a complex tile vs. many MB for tiff. Reading out PNG pixels can be done in client-side JavaScript these days.