It's worth noting that the reason the hash is used and not the raw token is because exposing the token itself in this way would be very insecure. So bybdefault we dont ship with that configuration.
It is possible to set up Tyk to not use hashes at all, you simply disable it in the tyk.conf and tyk_analytics.conf (you'll need to start over - the two modes are not compatible)
However, in this mode your users tokens, and associated metadata are stored in clear text in redis and in mongodb, any breach would expose your entire key set and you run the risk of leaking secure data through logs in proxies when making rest calls for data.
We don't recommend running in this mode unless you have isolated your data sources well and are only interacting with the dashboard via a secure env on a secure client.
We'll be extending the dashboard search feature to support token aliases - this should make it easier to search through hashed keys securely.