Verification Methodology

This page documents exactly how MC-Cheats sources, checks, and reports data about client files. The goal is transparency: users should be able to see what we verify, how we verify it, and — critically — what we cannot verify.

Step 1 — Sourcing

Every client page lists the origin of the file: a GitHub release, an official website, or another public distribution channel. We do not accept files from third-party mirrors, unofficial reuploads, or sources that cannot be tied to the original developer. If a developer publishes only through a private channel (Discord, paid dashboard), we link to that channel rather than mirroring the file.

Step 2 — Hash computation

We compute the SHA-256 hash of every file we document. SHA-256 is a cryptographic hash function that produces a fixed-length output for any input. Any change to the file — even a single byte — produces a different hash. This lets users confirm that the file they downloaded is identical to the file we documented.

Hash computation is done locally on the file after download. We do not rely on hashes published by third parties without independent verification.

Step 3 — VirusTotal lookup

VirusTotal aggregates results from 60+ antivirus engines. When a file has been previously submitted, VirusTotal returns a scan report. We link to that report and record the detection count at the time of writing.

Important: VirusTotal does not scan files on our behalf. If a file has never been submitted, there is no report. We do not submit files ourselves without explicit developer consent, and we do not treat absence of a report as evidence of safety.

Step 4 — Metadata recording

For each file we record: file size, file type, source URL, the SHA-256 hash, and — where available — a VirusTotal report link and detection count. If a piece of data cannot be verified, we omit it rather than guess.

What we do not verify

• Runtime behavior. We do not run client files. We cannot observe what a file does at runtime.
• Server-side effects. We do not test files on live servers. Detection behavior on specific servers is not guaranteed.
• Long-term safety. A file that is clean today may be replaced with a malicious version tomorrow by the developer. Our hash records the state at a specific point in time.
• Completeness of VirusTotal results. Detection engines miss malware. A clean report is not a safety guarantee.
• Legal compliance. We do not verify whether files comply with Minecraft's terms of service or any server's rules.

Update cadence

Client pages are reviewed weekly. When a developer publishes a new version, we recompute hashes and update metadata. When a file is pulled by the developer or replaced, we update the affected page and note the change in the changelog.

Corrections

If you find incorrect data on any page, use the correction link at the bottom of that page or the report issue form. We investigate every correction and update the page when warranted.

Why this approach

Many sites make absolute claims: "100% safe", "virus-free", "undetected". These claims are not verifiable. They may be true in a specific moment, but they cannot be proven for all time. By documenting the specific checks we perform, we give users the tools to make their own decision rather than relying on an unverifiable promise.