There seems to be some kind of user-agent content cloaking happening on your site.
While I can directly go to https://thecount.com/2017/05/09/afshin-bahrampour-synagogue-fires-sex-offender/amp/ in my browser, the AMP validator seems to get redirected to the non-AMP version, as can be seen at: https://validator.ampproject.org/#url=https%3A%2F%2Fthecount.com%2F2017%2F05%2F09%2Fafshin-bahrampour-synagogue-fires-sex-offender%2Famp%2F
Compare making a request as the AMP validator:
$ curl -sA "Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MTC19V) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.81 Mobile Safari/537.36 (compatible; validator.ampproject.org) AppEngine-Google; (+https://code.google.com/appengine; appid: s~amp-validator)" https://thecount.com/2017/05/09/afshin-bahrampour-synagogue-fires-sex-offender/amp/ | head -n 2
<!DOCTYPE html>
<html lang="en-US">
Versus making a request as a regular desktop Chrome on a Mc:
curl -sA "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" https://thecount.com/2017/05/09/afshin-bahrampour-synagogue-fires-sex-offender/amp/ | head -n2
<!doctype html>
<html amp lang="en-US">
The former serves a non-AMP response whereas the latter does.
So this would not be an issue with the AMP plugin but rather is probably another one of your plugins is doing.
