About MC-Cheats

MC-Cheats is a reference database for Minecraft clients, cheat modules, and their compatibility across Minecraft versions and servers. The site exists to provide verifiable data, not to make claims that cannot be checked.

What this site is not

• Not a download portal for pirated software.
• Not an endorsement of using clients on servers that prohibit them.
• Not a substitute for server rules. Server rules override anything on this site.
• Not a source of "undetectable" or "100% safe" claims. Those claims cannot be proven.

How the database is structured

The database is organized around entities (clients, cheat modules, Minecraft versions, servers) and views (categories, compatibility matrices, status trackers). Each entity has its own page with verified data and a last-checked date. Each view aggregates entities by a shared attribute.

See the database index for a complete overview of entities.

What we verify

• Source links — every client entry links to its official repository or website.
• Status labels — Active, Updated, Stale, Discontinued, or Unknown, based on public repository activity.
• Version support — which Minecraft versions each client works on, based on release notes and changelogs.
• File metadata — SHA-256 hash, file size, and type where available.
• VirusTotal data — detection counts and report links where reports exist.

What we do not verify

• Runtime behavior of any client file.
• Compatibility of every module on every server.
• Long-term safety of any file. A file that is clean today can be replaced tomorrow.
• Completeness of VirusTotal reports. Detection engines miss malware.
• Legal compliance with Minecraft's terms of service or any server's rules.

Full methodology: verification methodology.

Editorial principles

• No unverifiable claims. We do not publish "100% safe", "undetected", or "best" claims.
• Source first. Every factual statement links to a public source.
• Timestamps required. Status, version support, and file metadata all carry a last-checked date.
• Corrections welcome. Every page has a correction link. Reported issues are reviewed.

Full policy: editorial policy.

Contact

For corrections, suggestions, or security reports, use the contact page. For security-specific reports, use the report issue page.

Acknowledgments

This database would not exist without the work of client developers who publish their source code, write changelogs, and tag releases. Their transparency makes verification possible.