Trust & Proof: MyCrypto – Signal Evidence & AI Readability

MyCrypto

(https://mycrypto.com) 📸 Data Snapshot: May 24, 2026
Trust & Proof — The Lens

Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.

Trust & Proof Verifiable evidence vs. Trust Theatre.
13 Impact Weight: 20 / 100
65% Reputation

The homepage features six high-profile testimonials from industry figures like Nick Johnson and Tim Coulter, which provides strong social proof. However, these are recorded with a proof_links_count of only 2 across the main pages, meaning the majority of these endorsements lack direct links to verifiable third-party sources. The review_count of 4 against a lack of external validation links on the primary signal page suggests a reliance on static ‘trust theatre’ rather than live verification.

The proof density is top-heavy, relying on named industry testimonials and a specific mention of the ’50M+ labeled accounts’ database. Outside of these points, the site relies on vague assertions of being ‘the most secure’ and ‘usable’ without comparative data or independent audit reports. The presence of ‘CryptoScamDB’ as a sister product adds legitimate substance, but its integration as a proof point for the wallet’s current efficacy is weak.

Trust & Proof is read by weighing trust language against real verification. Below is the page-by-page tally of review mentions and external proof links, then the schema markup that may (or may not) declare verifiable ratings and identity proof.

🛡️ Trust Signals — reviews, proof links, trust-theatre check
13Review mentions (all pages)
13External proof links (all pages)
PageReviewsProof links
/ (home) 4 2
/privacy/ 4 7
/about/ 2 2
/jobs/ 3 2
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/privacy/ — no schema detected (entity gap)
/about/ — no schema detected (entity gap)
/jobs/ — no schema detected (entity gap)