Quick answer: In the first six days of July 2026, MEXC's official ST Warning announcement added 32 tokens across four separate dated batches: SABAI on July 1, three tokens on July 3, a 27-token batch on July 6, and PENDULUM on July 6 with its delisting date still marked TBC. June 2026 was even busier, with at least 39 tokens tagged across roughly 16 separate sub-announcements spanning June 1 to June 13. Most tags carry a fixed delisting date exactly 3 days later; a TBC tag means MEXC has flagged the token but has not yet decided the delisting date, which is a meaningfully different, and slightly more recoverable, situation.

‍

Most content on MEXC's ST Warning system explains the rule once and stops there: get tagged, you have about 3 days, then delisting. What almost nobody publishes is what the list actually looks like month to month, because MEXC updates it constantly and most guides go stale within weeks. This is a running read of the real, dated announcement data, updated for July 2026.

What the ST Warning List Actually Is

MEXC's ST Warning list is not the same thing as the Assessment Zone. The Assessment Zone is a 30-to-60-day pre-warning window where a token is flagged for review but still trades normally. The ST Warning list is the next stage: MEXC has already applied the ST tag, published the token publicly in a dated announcement, and started the delisting clock, which is typically 3 days from the tag date unless the announcement marks the delisting date as TBC (to be confirmed).

MEXC publishes these as standalone monthly announcement pages, each one accumulating every batch tagged that month. That means the list is a live, growing document for the first few weeks of every month, not a single one-time notice.

July 2026, Batch by Batch

As of the first week of July 2026, MEXC's July ST Warning announcement showed four separate dated batches:

• July 1 — SABAI. Tagged July 1, delisting date July 4. A single-token batch.
• July 3 — CLAW, 3KDS, PITCH. Three tokens tagged together, delisting date July 6 for all three.
• July 6 — a 27-token batch. The largest single wave of the month so far, including ADO, RIZ, DOGEUS, WORLDCUP, and BABYBONK among the 27, all sharing a delisting date of July 9.
• July 6 — PENDULUM. Tagged the same day as the 27-token batch, but listed separately with its delisting date marked TBC rather than a fixed date.

That is 32 tokens in six calendar days. The pattern already visible: MEXC does not spread tags evenly through the month. It clusters them into a handful of dated waves, with the size of each wave varying from a single token to dozens at once.

June 2026 Was Even Bigger

The prior month's announcement tells a similar story at a larger scale. MEXC's June 2026 ST Warning page recorded at least 39 tokens across roughly 16 separate dated batches between June 1 and June 13, including MOGU, BSW, TEN, RDNT, RBT, NTMPI, CRTR, SUNRISE, RAGEGUY, PIG, INI, LUM, SOLX, MLXC, and PACT as individual or small-batch tags, a single 20-token batch on June 11 that included LETSBONK, SIGMA, and WNXM, a three-token batch covering PART, EPIKO, and VEX, and a standalone tag on CERE.

Two months of real data point to the same conclusion: MEXC's ST tagging volume is not a rare event. It is a routine, high-frequency part of how the exchange manages its listed token base, running dozens of tags through multiple waves inside the first two weeks of nearly every month.

How This Compares to Binance's Monitoring Tag

The contrast with Binance is stark. Binance's Monitoring Tag reviews run in widely spaced waves, roughly nine weeks apart in the most recent documented cycle, and each wave typically adds a handful of tokens, not dozens. MEXC ran through more tokens in the first six days of July 2026 alone than Binance added across its entire January-to-March 2026 review cycle.

This is not a judgment on which exchange is stricter. It reflects a structural difference: MEXC lists a much larger volume of smaller-cap and newly launched tokens, so its risk-monitoring system processes a correspondingly larger and faster-moving list. For a project, the practical takeaway is the same either way: assume the review cycle you are on is short and frequent, not annual.

What TBC Actually Means

Most tagged tokens in both July and June carry a fixed delisting date exactly 3 days after the tag date. PENDULUM's July 6 entry is the exception worth understanding: a TBC delisting date means MEXC has applied the ST tag and published it, but has not yet locked in when trading actually stops.

That is not a loophole, but it is a real, if narrow, difference in urgency. A fixed 3-day date means the clock is already running. A TBC date means MEXC is still finalizing its decision, which is the narrowest possible window a project has to show measurable improvement before that date gets set.

What to Do If Your Token Shows Up in a Batch

1. Check the exact batch your token landed in and note whether the delisting date is fixed or TBC. That distinction changes how much time you actually have.
2. If the date is fixed, treat it as final. Three days is not enough time to fix holder count or volume from scratch, so focus immediately on whatever single metric is most likely to be reviewed.
3. If the date is TBC, move fast on visible, verifiable liquidity and volume improvement. This is the window where MEXC is still deciding, and measurable order-book activity is the fastest signal you can produce.
4. Contact MEXC's listing or business development team directly with evidence already in motion, not a plan. Teams that show live data move differently through review than teams that ask for more time.

Why This List Matters More Than a One-Time Guide

A static explainer of MEXC's ST rules goes out of date the moment the next batch posts. The actual list changes weekly. Projects trying to gauge their own risk are better served by watching the real cadence, dozens of tokens moving through multiple dated waves every month, than by a single static description of the process written once and never revisited.

Frequently Asked Questions

How many tokens get ST tagged on MEXC in a typical month?

Based on June and July 2026 data, the range is roughly 30 to 40-plus tokens per month, though the count is not evenly spread. Most tags cluster into a handful of dated batches within the first two weeks of the month.

Is a TBC delisting date better than a fixed one?

It suggests MEXC has not finalized its decision, which gives a tagged project slightly more room to show improvement before a date is set. It is not a guarantee of a longer timeline, and it can still convert to a fixed date at any time.

Does getting tagged in a large batch mean less individual scrutiny?

No. Batches are a publishing convenience for MEXC, not evidence of a lighter review. Tokens in the 27-token July batch and the 20-token June batch faced the same criteria as tokens tagged alone.

How does MEXC's ST Warning list differ from the Assessment Zone?

The Assessment Zone is the earlier warning stage, typically 30 to 60 days, before any public tag is applied. The ST Warning list is the later, public stage where the tag is already live and a delisting date, fixed or TBC, is attached.

Where can I check if my token is on the current list?

MEXC publishes each month's ST Warning batches as a running announcement on its official announcements page, updated as new batches are added throughout the month.

Tracking your own token against MEXC's next batch? Talk to EasyMM about getting continuous liquidity coverage in place before the next ST Warning wave posts.