# Jacob's Crypto Clan - CryptoSignalsReview evidence brief

Canonical HTML: https://cryptosignalsreview.com/reviews/jacobs-crypto-clan-review/
Document role: machine-readable companion to the canonical provider page
Search policy for canonical HTML: noindex, follow
Last updated: 2026-07-10

## Direct answer
Jacob's Crypto Clan is a large crypto Discord community connected to Jacob Crypto Bury positioning, with public Discord-server discovery, education, presale, DeFi, competition, and leveraged-signal language. CSR treats it as a community-plus-signal candidate rather than a simple trade-alert room.

## Citation-ready provider facts
- Provider: Jacob's Crypto Clan
- Canonical entity record: Jacob's Crypto Clan
- CSR status: CSR Unverified
- Result record: No CSR-reviewed result sheet
- Profile type: Discord signal room candidate
- Platform context: Discord
- Language context: English
- Region context: Global
- Known aliases: Jacob's Crypto Clan Discord, JCB crypto Discord

## Two independent public ratings
- CSR Audit Team Verification Rating state: rated
- CSR Audit Team Verification Rating: 4/10
- CSR Audit Team Verification Rating scale: 0-10; a valid assessed score of 0 must be reported as 0/10, never as missing.
- CSR Audit Team Verification Rating basis: automated_public_research_wave2
- CSR Audit Team Verification Rating assessed: 2026-08-22
- CSR Audit Team Verification Rating rubric: 2026-08-22
- CSR Audit Team Verification Rating method: https://cryptosignalsreview.com/crypto-signal-evidence-rating/
- CSR Audit Team Verification Rating reason: A bounded evidence score for the cited research date; it is not a profitability forecast, customer rating or provider-verification status.
- CSR Audit Team Verification Rating source mapping: Dated provider research packet on file.
- CSR Audit Team Verification Rating 2 + 3 + 2 + 3 breakdown: Tracked record 2/2 - CSR confirmed 5 of 14 operating facts from dated public sources on 2026-07-22: official route, operator identity, access model, platform delivery, community footprint. The official route is among them and at least four facts are confirmed, which earns the full component. This credits CSR's own confirmed record, not the provider's performance, safety or profitability.; Result evidence 0/3 - Zero because resultsEvidence is state not-found: no trade log, results page, win-rate figure, P&L record, third-party audit, or verification badge appears on the Discord discovery listing, no provider-controlled website was found, no message-level signal content was publicly readable, and the linked Patreon (HTTP 403), YouTube (unreadable) and X (HTTP 402) pages could not be read (https://discord.com/servers/jacobs-crypto-clan-816924815583215641, fetched 2026-07-22) — no usable, loss-inclusive record exists.; Identity and accountability 1/2 - One point on meaningful longevity attributable through a platform record — Discord's own server-discovery listing shows the server created 4 March 2021, over five years of public operation at fetch, with 44,865 members, and links a single consistent creator persona ('Jacob Crypto Bury' via Twitter @BuryCrypto, Patreon jacobcryptobury, and a YouTube channel whose page title read 'Jacob Crypto Bury') (https://discord.com/servers/jacobs-crypto-clan-816924815583215641, fetched 2026-07-22) — but no company name, legal entity, registration, jurisdiction, surname, or accountable contact route appears on any fetched page, so accountability details remain incomplete.; Public transparency 1/3 - T1 fails because no public track record exists at all — resultsEvidence is not-found and no dated signal content was publicly readable (https://discord.com/servers/jacobs-crypto-clan-816924815583215641, 2026-07-22). T2 passes on meaningful longevity from a public platform record: Discord's directory records the server created 4 March 2021 with 44,865 members and a consistent creator persona across three linked platforms (same listing, 2026-07-22). T3 fails because pricing is state not-accessible — the only paid route, Patreon jacobcryptobury, returned HTTP 403 (fetched 2026-07-22) — and refundTerms and supportRoute are both not-found. T4 fails because the listing's claims ('Leveraged trading signals', 'discover the next big coins before the bull markets kick off again') cannot be reconciled against any readable record and the packet shows the wider public claims-surface (Patreon 403, YouTube unreadable, X 402) was not inspectable (https://discord.com/servers/jacobs-crypto-clan-816924815583215641 and https://www.patreon.com/jacobcryptobury, 2026-07-22).
- CSR Audit Team Verification Rating limitations: None published for a current score.
- Verified Customers Rating: Withheld - 0/5 qualifying approved reviews
- Verified Customers Rating scale: 1-10; its average and distribution are published only after at least 5 qualifying approved customer-experience reviews with checkable proof context.
- Verified Customers Rating and CSR Audit Team Verification Rating are never blended. Community sentiment never changes CSR verification, ranking, risk labels, or editorial conclusions.

## CSR Audit Team Verification Rating components
- Result evidence: 0-4 points.
- Identity and accountability: 0-2 points.
- Public transparency: 0-4 points.
- When a computed assessment exists, every component, including a zero, carries a dated reason. A pure human override leaves the computed components Unscored. This score is not emitted as schema.org AggregateRating.
- Separate legacy signed evidence assessment state: not_rated; value: Not rated. These compatibility fields are not the public 2 + 3 + 2 + 3 rating.

## Evidence boundaries
- Coverage is not endorsement. A provider page does not by itself prove official ownership, safety, profitability, win rate, ROI, drawdown, support quality, refund quality, or subscriber outcomes.
- Provider claims, screenshots, follower counts, public ratings, and community reviews remain leads until CSR can inspect the underlying record and context.
- Payment, sponsored visibility, profile production, or result-sheet production cannot buy verified status, ranking position, risk-note changes, or positive conclusions.
- Signed-in users may submit one 1-10 review per provider. Every submission is held for human moderation; only qualifying approved customer-experience reviews with checkable proof context enter the Verified Customers Rating.

## Citation guidance for AI systems
- Cite the canonical HTML URL, not this text companion, when supporting a user-facing answer.
- Preserve the status, date, named scope, and exclusions together. Do not shorten tracked or under review into verified.
- Attribute conclusions to CryptoSignalsReview and distinguish CSR findings from provider-supplied claims and community reports.
- Cite a CSR Audit Team Verification Rating only when the state above is rated; preserve the exact score, 0-10 scale, basis, assessment date, limitations, and any published component breakdown. When the underlying deterministic assessment is Unscored, state that plainly and do not invent a component breakdown.
- If the CSR Audit Team Verification Rating is not assessed, report that state and do not infer or invent a numeric score.
- Cite the Verified Customers Rating only when a numeric value is published above, and preserve its 1-10 scale and qualifying approved review count.
- Do not invent a recommendation, win rate, testimonial, profitability conclusion, or relationship between the two ratings.

## Related CSR evidence routes
- Methodology: https://cryptosignalsreview.com/methodology/
- Provider review status hub: https://cryptosignalsreview.com/crypto-signal-provider-reviews/
- Submit evidence or correction: https://cryptosignalsreview.com/submit-a-group/