What Mizan returns and how to get it

Every Mizan record holds an account's bans from the community ban lists Mizan reads and, for a Steam account, Steam's own bans. Here is what each record holds, every way to read it, how fresh it is and what it can't tell you.

Last updated October 30, 2026.

What a record holds

Every account Mizan knows has a record at https://mizan.ac/players/{platform}/{id}. A lookup reads Steam, Discord, Minecraft, FiveM, Epic Games, Xbox, Epic Online Services accounts. The record's verdict counts bans in the lists' own words, such as "Banned on 2 lists, both in force". It never calls the player a cheater, and only Mizan's own anti-cheat ever "caught" anyone.

The page shows all of it. Its .json and .md forms carry the verdict, Steam's record, the bans and the ids, and leave out the linked accounts and profile facts.

Where the bans come from

Mizan reads Community Ban List (Squad), Chronon Labs, SteamRep (2024 archive), rust-admin.ru shared list, ARK: Survival Ascended official bans (Studio Wildcard) and 563 other lists: 5,066,841 bans, 4,465,928 of them in force, across 21 games. These figures were read on October 31, 2026 at 08:53 AM UTC.

Most lists are SourceBans pages that game communities publish. Others are other ban panels, files a community publishes, a game developer's own list, or an anti-cheat's detections. Organizations registered on Mizan can also send their own bans through the API. Communities names every list and its bans, and How Mizan works says how each is read and what its labels mean.

How to get it

On mizan.ac

Lookup takes anything a player would paste: an id, a profile link or a name. The lobby check takes a server's status output or a list of SteamIDs and checks up to 100 Steam accounts at once. Neither needs an account.

As JSON or Markdown

Add .json or .md to a record's address, as in https://mizan.ac/players/steam/{SteamID64}.json, or ask for the page with Accept: application/json. Both forms answer with Access-Control-Allow-Origin: *, so a page on another site can read them. No key.

The API

With no key, GET /v1/public/players/{player} gives one player's public record, and GET /v1/stats, GET /v1/sources and GET /v1/health give the registry's size, its lists and whether it is answering. An approved community's key adds the rest: POST /v1/players/batch checks up to 1,000 players in one request, GET /v1/bans/changes follows every ban change from a cursor, GET /v1/steam/{player} reads Steam's record, and your servers report joins and add bans. The API reference has every route at https://api.mizan.ac.

For AI agents (MCP)

Mizan's MCP server is at https://mizan.ac/mcp (Streamable HTTP). Its read tools need no sign-in: lookup_player, check_players, list_sources and registry_stats. list_my_communities asks you to sign in to Mizan first. The server is described at https://mizan.ac/.well-known/mcp-server.json, and llms.txt tells an assistant how to word what it finds.

In Discord

Once a community adds the Mizan bot from its dashboard, anyone in that Discord server can run /mizan check with a SteamID, profile link, Discord id or Minecraft name, and /verify links a member's Steam account for a verified role.

On a Rust server

Point Rust's server.bansServerEndpoint at Mizan and the server refuses a player while a list's ban labelled cheating is in force on them. Rust centralized banning has the two lines of config.

Let players in by your own rules

A community's join policy decides what happens when a player joins one of its servers: log the join, flag it for staff, or refuse it. It answers "should this player get in" with the rules the community set, not with a score Mizan gives the player.

• Cheating bans: a ban labelled cheating from the last 365 days, or any span from 1 to 3,650 days, from any list or only lists for the same game.
• Conduct bans: log or flag, never refuse.
• Your community's own bans in force: refused unless you choose otherwise.
• Steam's bans: VAC bans, game bans, Steam Community ban, trade probation and trade ban.
• The Steam account: likely alt or resold account, new account, Steam level, earned badge XP, no Years of Service badge, default avatar, profile never set up, few friends, friends without avatars, few Steam groups, banned friends, private profile and private game details.

Every rule but the community's own bans starts at log only or allow, because refusing a real player costs more than missing a cheater. A server can set its own rules apart from the community's. A join Mizan could not check, because it was down or over a limit, is let in. Servers report joins through the API's POST /v1/joins. Join rules are in preview and open to communities one at a time.

Server plugins

Drop-in plugins for Garry's Mod, Counter-Strike 2 (CounterStrikeSharp) and Rust (Oxide and uMod) are being built. Until one is out for your game, a server reports joins through the API, and a Rust server can use centralized banning today.

Freshness and limits

• Most lists have their newest page read every hour and the whole list about once a day; a long or slow list is read weekly or in slices.
• The registry's counts are read once a minute.
• A record's page and its .json and .md are kept at the edge, so a copy can be up to an hour old.
• An API answer about a player is at most 60 seconds old on Mizan's side.
• Steam's record is kept up to six hours. Live Steam calls for a community's players go on its own Steam key, or on Mizan's within 100 a day.
• A record carries up to 200 bans; GET /v1/players/{player}/bans pages through all of them.

Compared with Steam-only ban checkers

A Steam ban checker reads Steam's own record of an account. Mizan reads the same record and adds the bans game communities publish, which Steam never sees: VAC only watches VAC-secured servers, and a community server bans cheaters on its own list.

What Mizan can't tell you: it sees only the lists it reads and the bans they publish, so a private list or a server's unpublished bans aren't on it. It doesn't review a list's bans; each is that community's claim, appealed to that community (disputing a ban). No bans found means none on the lists Mizan reads, nothing more.

Mizan on Steam profiles

A small userscript adds a few lines to Steam Community profile pages: the record's verdict, its cheating bans in force, Steam's VAC and game bans when the record carries them, and a link to the record on mizan.ac.

1. Install a userscript manager in your browser, such as Tampermonkey or Violentmonkey.
2. Open mizan.user.js; the manager shows what it does and asks you to install it.
3. Open any steamcommunity.com/id/… or steamcommunity.com/profiles/… page.

It runs only on those pages and reads only the open profile's .json from mizan.ac. It sends nothing else and stores nothing. The script is plain JavaScript you can read before installing.