Minecraft integrity,
clearly scoped.

Download the portable EXE

Unsigned staging preview · not a production release.Windows may show a SmartScreen warning because this build has not been Authenticode-signed.

V3.0 explicitly opts in to a signed, legacy ungoverned prerelease pack. That pack contains only nonmatching informational plumbing rules and no production cheat intelligence. Its signature protects pack identity and integrity; it does not supply the private sample dossiers, independent approvals, expiry, and rollback evidence required for production rules. This staging-only exception does not weaken the production governance or release gates.

This is one portable Windows x64 file. It needs no installer, administrator access, Go, Java, or separate runtime. It contacts only the public MaghrebSMP scanner API. The client never receives Discord credentials or an NVIDIA API key. Backend-only Discord delivery is enabled for authorized scan policies and is disclosed before consent. Optional NIM review runs only when the request-specific consent notice says it is enabled.

For the private staff-report policy, the consent summary also states that the accepted minimized report is encrypted on the backend for no longer than 720 hours after scan completion. The staff Discord message receives a code-free report link and a separate high-entropy case key. The page reveals no result until that key is accepted; the key is sent only in an HTTPS POST body and is never put in the URL or browser storage.

The compact native Windows interface has one dominant Scan button, one short status, and a dark progress view. Full scope and result text stays available under Details without filling the default screen. While collectors run, the activity bar remains indeterminate because the remaining work is not knowable; it shows 100% only after the backend accepts the completed report.

1. Download and verify the SHA-256 shown here.
2. Start one Minecraft Java instance and keep it open, then run the EXE as your normal Windows account. Multiple plausible JVMs or no uniquely corroborated target make the runtime checks incomplete.
3. Wait for the app to verify its short-lived scanner capability and signed staging rule pack.
4. Open Details to read the exact disclosure, then click Scan. No ticket is required.

V3.0 attempts to pin exactly one active Minecraft JVM, canonical game directory, declared JAR classpath, active version lineage, declared -javaagent/-agentpath files, local-only -agentlib signals, and Toolhelp-visible modules. It can also recognize a renamed Windows JVM host only when the same PID owns an exact GLFW/LWJGL window and exposes an adjacent, loader-visible jvm.dll in a normal runtime layout. Its Windows launch parser recognizes Minecraft 26.2's documented Java 25 unsafe-memory option and safely handles long classpath arguments within the Windows command-line limit. An unreadable or truncated same-user Java candidate remains fail-closed; V3.0 preserves the exact path-free failure category for staff. If no target can be pinned, current mods, installed versions, and bounded latest.log evidence are still collected only from validated launcher roots or the exact folder you chose; those fallback checks remain incomplete. Local paths stay local and raw command lines are discarded.

V3.0 gives current official client archives more bounded structural headroom and sends the loaded-module collector directly to the already pinned JVM. Module review now runs as three explicit stages: Windows snapshot, SHA-256 fingerprinting, and Authenticode classification. A stable-identity cache is limited to the current scan, and staff can see the exact stage that timed out instead of one generic incomplete result.

V3.0 includes a signed, fail-closed format for version-specific Mojang, loader, library, native, launcher, overlay, and signer baselines. This staging download does not yet contain reviewed production baseline identities: the checked-in empty example trusts nothing, and unknown or mismatched files are never automatically labeled as cheating.

V3.0 can inspect a maximum of 64 Minecraft mod-history facts from only the current Windows user's Recycle Bin. Each accepted fact contains only a normalized JAR basename and the UTC time Windows recorded the item moving into the Recycle Bin. The scanner does not open, recover, hash, or upload the retained deleted-file content or its original path.

This history coverage is supplemental and non-verdict-gating: partial or unavailable Recycle Bin visibility does not make the required scan incomplete. It cannot observe Shift+Delete, an emptied Recycle Bin, another user's items, or universal deletion history. A basename, move time does not by itself prove that a mod was loaded or used, that anyone cheated, or that anyone attempted evasion. Recycle Bin metadata is current-user-modifiable historical context, not trusted proof.

Every accepted completed staff report includes a fixed 1200×1200 PNG summary card rendered by the backend from the already accepted structured fields. It is not a client, desktop, or gameplay screenshot. When any of the up to 512 normalized mod-JAR names accepted by the report are present, the backend also generates one bounded current-inventory text attachment containing every accepted name. Accepted Recycle Bin facts are placed in a separate bounded mod history attachment. A listed JAR is inventory context, not proof that it was loaded or used. The card summarizes governed detections, injection-check coverage, and the optional NIM advisory without allowing model output to change the deterministic verdict.

Do not disable antivirus. V3.0 reports declared device-check completeness separately from live game/server-session association. A completed self-service scan remains unbound and is never session-level clearance. It does not inspect process memory, read raw target-JVM environment variables, recover deleted files, or claim to detect every cheat. Scoped current-user Recycle Bin metadata is not deleted-file recovery.