Both were used by multiple users back at the time, and we managed to integrate the test results of the projects (PHP, Java, and some JavaScript) through TAP in Jenkins, reporting the test coverage too (in the YAMLish, which is not exactly part of the TAP spec, unless the latest release included it)
I first saw it used with JavaScript, so I assume yes; but the site itself answers this, too. (specifically the producers and consumers pages.)
I think it is of limited use if you can use any of the more sophisticated defacto standards like JUnit compatible output. Still, you can imagine scenarios where a stupidly simple test protocol would be nice. One fairly esoteric use case might be test ROMs for CPU emulators; today many of them output results to serial in some format, but AFAIK there is no unification of the format at all, across different test ROMs.
Am I missing something? I was actually recently looking into BDD-like tools recently, so I feel like I'm a potential user for TAP, but I just can't grok the value add in it offhand.
edit: oh, maybe TAP is the inverse of what I was thinking. It's about output of test suites, for common post-test tooling? Aka to give statuses about the state of tests?