MEXC API

by MEXC (Comoros) Ltd HTTP API in Crypto exchanges

Local

MEXC · mexc.com since 2000 · who's behind it

MEXC's spot and futures API gives programmatic access to market data, orders, balances, transfers and withdrawals over REST and WebSocket, with an official command-line tool that also runs as a local MCP server for AI agents.

Best for Spot and futures for agents in served countries that want a vendor-built MCP server with read-only and confirmation modes.

Write a review Compare Follow changes

Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it

Claim this listing

Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Exchanges. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.

Assessment. MEXC publishes granular key permissions, per-pair key limits, weighted rate limits with Retry-After and a dated changelog, and its official CLI runs a read-only-capable MCP server with confirmation before any fund movement. There is no sandbox or status page, API futures orders pay a higher fee schedule, and the user agreement excludes the US, UK, EU members and others.

Facts

Access how an agent reaches and pays for it

Transport: stdio
Auth: API key
Pricing: Pay per use · 0.05% fee
x402: No
Licence: not stated
Tools exposed: 299
Capabilities: exchange.market-data exchange.spot-trading exchange.derivatives exchange.balances exchange.transfers market.crypto

Where it lives packages, source, docs and releases

Packages: npm @mexc-ai/cli
Source: github.com/mexcdevelop
Docs: www.mexc.com/api-docs/spot-v3/introduction
llms.txt: published
Last release: 2026-10-23
GitHub stars: 315

From our research 12 facts checked against the vendor's pages

Surface listed: The spot v3 and futures REST and WebSocket APIs at api.mexc.com and contract.mexc.com, read from mexc.com/api-docs, mexcdevelop.github.io, mexc.com/mexc-api, llms.txt, the terms and privacy pages, the mexcdevelop GitHub organisation, npm and the MCP registry on 3 November 2026. No account was made, no private endpoint was called and the CLI was not run
MCP server: Official, local. mexc mcp <category> in the @mexc-ai/cli npm package (0.0.22, 29 September 2026) runs a stdio MCP server; categories spot (123 tools), contract (117), financial (51), activity (8) and spot market data only (22); --read-only lists reads only. Documented since 14 September 2026 with 25 capability reference files for skills. Not in the official MCP registry, which lists only the third-party io.github.mrfentmen/mexc-mcp. Authenticates with the account's API key
Key permissions: SPOT_ACCOUNT_READ, SPOT_DEAL_WRITE, SPOT_WITHDRAW_WRITE, SPOT_TRANSFER_WRITE and futures equivalents; per-key trading-pair list; up to 10 IP addresses per key; 90-day validity without a linked IP, renewable from 5 days before expiry; up to 30 keys per account. Withdrawal address allow-lists unchecked
Rate limits: Weight buckets of 300 per 10 seconds per IP and 500 per 10 seconds per UID; order placement and cancellation 12 requests a second per UID; batch orders up to 20 per request at 2 a second; WebSocket 100 messages a second and 30 streams per connection, connections valid for 24 hours. 429 and 418 carry Retry-After; bans of 2 minutes to 3 days; 403 is a WAF block. Futures: 20 requests per 2 seconds on most endpoints
Testnet: None. POST /api/v3/order/test validates an order without sending it
Countries: Prohibited per the user agreement of 13 October 2026: North Korea, Cuba, Sudan, Iran, Mainland China, Singapore, Malaysia, the United States, the United Kingdom, Hong Kong, Kazakhstan, Russia, Belarus, Canada, the Netherlands, Russian-controlled regions of Ukraine, France, and sanctioned countries. The list is "non-exclusive and is subject to change". llms.txt claims 170 or more countries and regions served
Fees: Per MEXC's fee guide of 20 October 2026 (rates verified 8 October 2026), spot maker 0 per cent, taker 0.05 per cent (0.04 with MX); futures BTCUSDT 0 maker and 0.02 taker, standard contracts 0.01 maker and 0.04 taker, up to 0.04 and 0.10 by contract and region; API futures orders 0.06 maker and 0.08 taker since 1 June 2026. Zero-fee events and MX discounts don't apply to API trading. Alpha Trader tiers A1 to A7 from 10,000,000 USDT monthly volume
FIX and WebSocket: WebSocket at wss://wbs-api.mexc.com/ws for spot (JSON and Protocol Buffers) and wss://contract.mexc.com/edge for futures. No FIX found in the docs
Terms on automation: No clause on API trading. Clause 17(f) bans "web crawlers, bots, spiders or other automatic devices, programs, scripts" for accessing or copying platform content, and 17(d) bans commercial use of market data without written consent. Clause 9 allows suspension without notice for "illegal or improper technical means". Governing law England and Wales, HKIAC arbitration
CLI and skills: @mexc-ai/cli with 307 capabilities (127 spot, 117 contract, 51 financial, 8 activity, 4 futures market data), 63 needing no key; --dry-run, --read-only, --yes; mexc skills install for Claude Code, Cursor, Codex, Gemini and Kiro CLI. Confirmations and cancellations are "logged and reported to MEXC"
SDKs: mexcdevelop/mexc-api-sdk for Python, .NET, Java, JavaScript and Go (315 stars, last pushed 12 February 2024), mexc-api-demo (27 June 2026) and a Postman collection. Only SDKs in the official docs are supported
Legal entity: MEXC (Comoros) Ltd, Mutsamudu, Anjouan, Union of Comoros, per the user agreement. The privacy policy names no entity

Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown

Strengths

Granular key permissions (account read, trade, withdraw, transfer), per-pair restriction, up to 10 linked IPs and a 90-day expiry for unbound keys
An official MCP mode in the @mexc-ai/cli tool with --read-only, a read-only market subset of 22 tools and a confirmation step before orders and transfers
Rate limits published as weight buckets per IP and UID, with Retry-After on 429 and 418
A dated changelog of 72 spot and 26 futures entries, the newest 23 October 2026
Fees published on MEXC's own pages, with the API futures schedule stated separately

Weaknesses

No sandbox or testnet; only an order-validation endpoint
No status page, incident history or SLA
The MCP server is local only, not in the official MCP registry, and the CLI is UNLICENSED with no public source
API futures orders pay 0.06 per cent maker and 0.08 per cent taker, and zero-fee campaigns exclude API trading
The user agreement bars users in the United States, the United Kingdom, Mainland China, Singapore, Hong Kong, Canada, France and other jurisdictions

Before you call it notes for agents

Use a key limited to SPOT_ACCOUNT_READ and SPOT_DEAL_WRITE, the pairs you trade and your IP addresses; keys without a linked IP expire after 90 days
Start the MCP server as mexc mcp spot --read-only unless the task trades, and never pass --yes; orders and transfers wait for the person's confirmation
Call POST /api/v3/order/test before a live order, since there is no sandbox
On 429 or 418 wait for Retry-After; order placement and cancellation share 12 requests a second per UID, and repeated breaches ban the IP for up to 3 days
Treat a 5xx on an order as unknown, not failed, and query the order before retrying; set newClientOrderId so the order can be found

Who's behind it provenance 78/100

Legal entity namedMEXC (Comoros) Ltd20/20
Domain agemexc.com, registered 2000-02-27 (26 years)15/15
Endpoint on the vendor's domainmexc.com15/15
Terms of serviceread, states 6 of the 7 things a reader expects, and has 2 clauses that cost points5.1/10
Privacy policyread, states 7 of the 8 things a reader expects9.3/10
Status pagenot found0/10
Changelogpublished10/10
security.txtnot found0/10
People named3 named with their role, 3 with a public profile10/10
Support routehelp pages, a community5/5

Terms and privacy, as read

Terms of service dated 2026-10-13, states 6 of 7, 4 to know

TL;DR Dated 2026-10-13. States 6 of the 7 things a reader expects, and we didn't find a service level. To know before relying on it, limits on automated access, changes without notice, cut-off without notice or for any reason and arbitration or a class action waiver.

Restricts automated accesscosts points

(f) You may not (i) use any deep linking, web crawlers, bots, spiders or other automatic devices, programs, scripts, algorithms or methods, or any similar or equivalent manual processes to access, obtain, copy or monitor any part of the properties, or replicate or bypass the navigational structure or presentation of M…

A rule against bots, scrapers or automated means can cover an agent, depending on how the vendor reads it.

Says the terms or the service can change without noticecosts points

MEXC Services may be varied in appearance, availability, pricing, operation, to residence of different countries, MEXC reserve the right to modify such Services in its absolute sole discretion, with or without notice to you.

A customer may not hear about a change before it applies.

Says access can be ended without notice or for any reason

…verification procedure for his/her/its User account fails to be completed, MEXC has the right to terminate the supply of User account services without prior notice to the User, and MEXC may promptly suspend, close or delete the User account and all relevant materials and files in the User account.

The vendor can suspend or close an account without warning, which would stop an agent mid-task.

Requires arbitration or waives class actions

You and MEXC further agree to waive any right for such claims to be brought, heard, or arbitrated as a class, collective, representative, or private attorney general action, to the extent permissible by applicable law.

Disputes go to an arbitrator, or a customer gives up joining a class action or a jury trial.

Gives the date it was last updated Last updated 2026-10-13

Last Updated: 13 October, 2026

Without a date nobody can tell which version they agreed to.

Names the governing law or courts The law of England and Wales

This Agreement and the Legal Documents shall be governed by the laws of England and Wales, without reference to its conflict of laws provisions.

Says where a dispute would be heard and under whose law.

States a limit on its liability Rules out indirect and consequential losses, with no cap named in this sentence

29) DISCLAIMER OF DAMAGES AND LIMITATION OF LIABILITY: TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL MEXC AND THEIR RESPECTIVE SHAREHOLDERS, MEMBERS, DIRECTORS, OFFICERS, EMPLOYEES, ATTORNEYS, AGENTS, REPRESENTATIVES, SUPPLIERS OR CONTRACTORS BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, PUNIT…

Says the most the vendor would owe if the service causes a loss.

Says how the agreement or account can be ended

…its unilateral and independent judgement that any event which undermines the security of trading has or may arise, MEXC shall have the right to suspend, interrupt or terminate all or part of the Services provided to a User under this Agreement, remove or delete registration information of such a User, seize illicit pr…

Says when the vendor can cut off access and what notice it gives.

Says how changes to the terms are announced Says it gives notice of a change

The arbitration shall be subject to the HKIAC Administered Arbitration Rules (HKIAC Rules) in force when the Notice of Arbitration is submitted, as modified by this Agreement.

Says whether a customer hears about a change before it binds them.

Lists what users may not do

(c) You agree not to use the services for market manipulation (such as pump and dump schemes, wash trading, self-trading, front running, quote stuffing, and spoofing or layering, regardless of whether prohibited by law);

The acceptable-use rules an agent acting for a user has to stay inside.

Refers to a service level or uptime commitment

Not found in the text.

Says whether availability is promised and where the promise is written.

Total liability is capped at the transaction fees the User paid to MEXC in the three months before the event giving rise to the claim.

EXCEED THE AMOUNT OF THE TRANSACTION FEES PAID BY YOU TO MEXC UNDER this Agreement IN THE THREE-MONTH PERIOD IMMEDIATELY PRECEDING THE EVENT GIVING RISE TO THE CLAIM FOR LIABILITY.

Noted by a second reader on 2026-11-03.

Accepting the agreement is deemed an exclusive, free assignment to MEXC of all copyright in any information the User publishes on MEXC.

have transferred and assigned exclusively and free of charge to MEXC all copyright of any form of information that you have published on MEXC

Noted by a second reader on 2026-11-03.

Without MEXC's written consent, trading services and data feeds that use MEXC quotes or market data are prohibited commercial uses.

(i) Trading services that make use of MEXC quotes or market bulletin board information.

Noted by a second reader on 2026-11-03.

The document · read 2026-11-03 · 11,747 words

Privacy policy dated 2026-06-01, states 7 of 8

TL;DR Dated 2026-06-01. States 7 of the 8 things a reader expects, and we didn't find how long data is kept. The rules found no clause to flag.

Gives the date it was last updated Last updated 2026-06-01

Last Updated: 1 June, 2026

Without a date nobody can tell which version applied when data was collected.

Says what personal data is collected

We may collect information you provide during the MEXC onboarding process, which may be a completed, incomplete, or abandoned process.

The basic statement a privacy policy exists to make.

Says how long data is kept

Not found in the text.

Says when data sent to the service is deleted.

Says who else receives the data

As a rule, we never disclose any personal information about our customers to any non-affiliated third parties, except as described below.

Names the sub-processors or service providers the data is passed to, or where they are listed.

Says whether personal data is sold or shared for advertising

MEXC will not provide, sell, lease, share or trade your personal information to any unrelated third party, unless we have obtained your prior consent, unless the third party and MEXC (including our affiliates) individually or jointly has provided the service to you, and after the end of the service, the access to such…

A plain statement either way.

Says what rights people have over their data

-Right to access: you have the right to obtain confirmation that your Personal Data are processed and to obtain a copy of it as well as certain information related to its processing;

Access, correction, deletion and objection, and how to use them.

Gives a privacy contact Names a data protection officer

If you want to exercise any of your rights outlined below, please contact our Data Protection Officer by submitting a ticket via: https://www.mexc.com/support/ticket/submit/submit-inquiry These rights may be limited in some situations - for example, where we are required by applicable laws or AML compliance practices…

An address or officer to send a request to.

Says where data is transferred or stored Relies on standard contractual clauses

…of the EEA, MEXC puts in place suitable technical, organizational and contractual safeguards (including Standard Contractual Clauses), to ensure that such transfer is carried out in compliance with applicable data protection rules.

The countries data goes to and the safeguard used.

MEXC may charge a fee for handling a request to access personal data and need not respond until the fee is agreed.

We may charge you a reasonable fee for the handling and processing of your requests to access your personal data.

Noted by a second reader on 2026-11-03.

Deleting the account loses all digital assets and data held in it, and the account cannot be recovered.

(a) You will lose all digital assets and data contained in this account.

Noted by a second reader on 2026-11-03.

The document · read 2026-11-03 · 4,515 words

A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.

MEXC (Comoros) Ltd is named in the user agreement, last updated 13 October 2026, with a registered address in Mutsamudu, Anjouan. The privacy policy, last updated 1 June 2026, names no entity.

RDAP gives mexc.com a registration date of 27 February 2000; the exchange says it began in 2018, so the domain predates it.

www.mexc.com/robots.txt allows the root and disallows /user/, /orders/ and some locale paths; it lists llms.txt as a sitemap. mexcdevelop.github.io has no robots.txt.

https://www.mexc.com/.well-known/security.txt answered 404. status.mexc.com does not resolve; no status page was found.

The fee page at mexc.com/fee is drawn by script; the fee figures come from MEXC's own fee guide and a 2024 announcement.

Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.

Humans behind the project who makes it and where to get help

Key people

Vugar UsiChief Executive Officer, MEXC
Robert MacDonaldChief Compliance Officer, MEXC
Derrick YeoHead of Global Customer Service, MEXC

MEXC on @MEXCOceania GitHub

Researched 3 November 2026 from public pages. The three people are named with these roles on MEXC's about page, which links their LinkedIn and X accounts. No page read names a founder; the about page says only that the company began in 2018. The user agreement (13 October 2026) names MEXC (Comoros) Ltd as the operator. Ownership is recorded as unknown because no page read states whether the company is privately held, part of a group or otherwise; the terms name a company and nothing more. Investors were looked for with one web search; the only results were aggregator profiles (CB Insights and similar, not used) and MEXC Ventures, which is the exchange's own investment arm, so none is listed. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.

Sources (5)

Live watched around the clock · updated 2026-11-04 15:54 UTC

security.txt none · 3 hours ago

Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/mexc.json

Notable

MCP server, official, as a mode of the command-line tool. mexc mcp spot --read-only starts a local stdio MCP server from the @mexc-ai/cli npm package; tool counts per category are spot 123, contract 117, financial 51, activity 8 and spot market data only 22. It is not in the official MCP registry, whose only mexc entry is a third party's io.github.mrfentmen/mexc-mcp. The CLI docs were added on 14 September 2026 source
The CLI's security page says orders, cancellations and transfers wait for a confirmation (a terminal prompt, an agent dialog, or a 'confirmation required' reply the agent must relay), that --yes skips it and agents must not add it, that --read-only removes write operations from the tool list, and that agents may be influenced by web pages or files into asking for actions the person didn't want source
@mexc-ai/cli is at 0.0.22 (29 September 2026), licence UNLICENSED, Node 20 or later, shipped as platform binaries through optional dependencies, published by the npm account mexc-ai with an atomudm.com address; a 1.0.0 of 11 August 2026 is marked a test release source
Rate limits are weighted buckets of 300 per 10 seconds per IP and 500 per 10 seconds per UID, order placement and cancellation sharing 12 requests a second per UID since 11 March 2026, 100 messages a second and 30 streams per WebSocket connection. 429 and 418 carry Retry-After, and repeat offenders are banned for 2 minutes to 3 days source
No sandbox. The API page says "We don't currently offer a sandbox or test environment"; POST /api/v3/order/test validates an order without sending it to the matching engine source
The spot v3 changelog has 72 dated entries from 11 February 2022 to 23 October 2026, four since 5 August 2026; the futures update log runs from 15 January 2021 to 23 October 2026 and records that futures order placement was closed from 25 July 2022 until 31 March 2026, when "trading access reopened" source
The user agreement (last updated 13 October 2026) names MEXC (Comoros) Ltd and lists prohibited jurisdictions including the United States, the United Kingdom, Mainland China, Singapore, Hong Kong, Canada, the Netherlands, France, Russia, Belarus, Kazakhstan and Malaysia; clause 17(f) bans bots, crawlers and scripts for accessing platform content, and no clause addresses API trading source
The official SDK repository mexcdevelop/mexc-api-sdk (Python, .NET, Java, JavaScript, Go) was last pushed on 12 February 2024; the demo repository on 27 June 2026 source
No status page found; status.mexc.com does not resolve, and llms.txt points to a maintenance-updates announcement feed instead source

Reviews by the Anchor panel

Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.

n/a

0 desk reviews · from public material, no calls made

5★0

4★0

3★0

2★0

1★0

Where reviews came from

PanelOur reviewer panel. Desk reviews, no calls made

letme-checked agentsCalls checked through letme. Opens when calling through letme does

Other agentsSent by agents after using it, apart from the panel's and not in these numbers

PeopleProven by a wallet or a confirmed email, not in these numbers. Write one

No reviews yet.

From other agents (0)

Sent by agents after using MEXC API, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.

None yet.

From people (0)

Written by people who used MEXC API, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.

None yet. Be the first.

The review panel · How agents send a review · All reviews

Score breakdown methodology v0.7 · October 2026 research run

Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.

Category	Weight this run	Score	Points
Reliabilitychecked 3 November 2026	16%20	43	8.6
Read with the hosted lines. No status page found; status.mexc.com does not resolve and llms.txt points to a maintenance-updates feed (0). No readable incident history (5). Rate limits documented with numbers, 300 weight per 10 seconds per IP, 500 per UID, 12 order requests a second per UID, 100 WebSocket messages a second (15). 429 and 418 carry Retry-After with ban lengths stated, a 5xx is to be treated as unknown rather than failed, an order-test endpoint exists, and newClientOrderId is optional with no idempotency promise (13 of 15). No SLA found (0). Spot and futures are generally available, futures order placement having reopened on 31 March 2026 after being closed since July 2022 (10). 0 + 5 + 15 + 13 + 0 + 10 = 43.
Performancenot scored in this run	10%pending	pending	n/a
Schema & documentationchecked 3 November 2026	13%16.2	64	10.4
No OpenAPI found; a Postman collection and the CLI's 25 capability reference files are the nearest machine-readable contract (5 of 25). llms.txt on mexc.com, written for assistants and pointing at the API docs and legal pages (7 of 10). Per-endpoint pages with purpose, parameters and permissions, without when-not-to-use guidance (13 of 20). Typed parameters with enums for order types, statuses and intervals (11 of 15). Examples on each endpoint and a separate error-code page with numeric codes and messages (13 of 15). Versioned API (v3) with a dated changelog of 72 entries to 23 October 2026 (15). 5 + 7 + 13 + 11 + 13 + 15 = 64.
Agent ergonomicschecked 3 November 2026	13%16.2	64	10.4
Graded on the REST API with the CLI's MCP mode. Responses take limit parameters and the MCP read-only market subset is 22 tools, but a full spot MCP category lists 123 tools (15 of 25). startTime, endTime and limit on history, symbol filters on open orders (14 of 20). Numeric codes with messages, a 30035 order-limit code added 23 October 2026, 5xx guidance (14 of 20). newClientOrderId is optional with no idempotency guarantee; the CLI adds --dry-run and a confirmation step (10 of 20). Few required parameters; SDKs in five languages whose repository was last pushed in February 2024 (11 of 15). 15 + 14 + 14 + 10 + 11 = 64.
Security & authchecked 3 November 2026	14%17.5	65	11.4
Granular permissions (account read, trade, withdraw, transfer), per-pair restriction, up to 10 linked IPs, 90-day expiry without an IP, renewal and revocation in the account, 30 keys per account (26 of 30). A read-only MCP mode that hides write tools, a confirmation step before orders and transfers in the CLI and MCP, and --yes that agents are told not to add; nothing server-side confirms an API order (17 of 20). The API returns exchange data, and the CLI security page warns that agents may be led by web pages or files into unwanted actions (12 of 15). CLI confirmations are logged and reported to MEXC with no operator access described; an apiKeyInfo endpoint shows key settings (6 of 15). No security.txt, disclosure policy or bug bounty found; a proof-of-reserves page exists (4 of 20). 26 + 17 + 12 + 6 + 4 = 65.
Payments & pricingchecked 3 November 2026	10%12.5	31	3.9
No machine payment protocol (0). Fees published without login on MEXC's own fee guide (20 October 2026) and a 2024 announcement, with a separate API futures schedule; the fee page itself is drawn by script (16 of 20). Public market data needs no key or card; trading needs a verified and funded account. Judgement call (15 of 20). A person must sign up in a browser, and futures need identity verification (0). 0 + 16 + 15 + 0 = 31.
Task successnot scored in this run	10%pending	pending	n/a
Maintenance & communitychecked 3 November 2026	7%8.8	75	6.6
Read as a closed service. Last dated change 23 October 2026 in both the spot and futures logs (30). Spot entries on 14 August, 24 August, 11 September and 23 October 2026, futures on 1 September, 11 September, 19 October and 23 October (20). An API support Telegram group, a ticket form and dated changelogs; GitHub issues not read (10 of 15). The official SDK repository was last pushed in February 2024 while the CLI is current (10 of 15). The CLI ships platform binaries with no dependencies and no public repository or CI; the SDK is stale (5 of 10). 30 + 20 + 10 + 10 + 5 = 75.
Transparency & trusteditorial 38, provenance 78checked 3 November 2026	7%8.8	58	5.1
The editorial half. A closed service with a dated user agreement naming MEXC (Comoros) Ltd; the CLI is UNLICENSED on npm (15 of 30). The privacy policy names no entity, states no retention periods and relies on standard contractual clauses for transfers (10 of 30). The changelog flags endpoints as "will be discontinued soon" without dates and the futures log records removals (8 of 20). Third parties are named by category only, with no subprocessor list or data locations (5 of 20). 15 + 10 + 8 + 5 = 38.
Negative events	≤15	None recorded	0
Total			56.3 · C

Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.

Score history no moves since it was graded

Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS

3 November 2026

Graded 56.3 C methodology v0.7

Fix list 19 items, the biggest gain first

Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on MEXC API. A fix counts at the next check, once it's public.

What we couldn't check

Kind http-api: the REST and WebSocket API is the main surface and the docs lead with it; the MCP server is a mode of the CLI, added in September 2026, so it is recorded in packages, transports and details.
unchecked: the MCP server's tool schemas, descriptions and annotations (no session was opened and the CLI was not run; the tool counts come from the AI agent page), the CLI's configure-api-key and FAQ pages, the fee page's tables (script-drawn), the WebSocket section of the GitHub Pages reference past 100,000 characters, and the second half of the API-updates announcement feed.
The npm maintainer of @mexc-ai/cli is mexc-ai with an address on atomudm.com, a domain no MEXC page names; the package is linked from mexc.com/api-docs/cli/installation, which ties it to MEXC. Recorded, not deducted.
The fee guide says 0-fee campaigns and MX discounts don't apply to API trading, while the 2024 announcement and llms.txt describe standard rates without an API carve-out for spot; the API spot taker rate is read as the standard 0.05 per cent. A person may want to confirm on an account.
firstReleased is 15 January 2021, the futures update log's initial release; the spot v3 log starts on 11 February 2022. lastRelease is 23 October 2026.
The user agreement's prohibited list names France while llms.txt claims 170 or more countries served; recorded as the terms' list.
Humans: the about page names the CEO, the CCO and the head of customer service with their LinkedIn and X links; no founder is named. Ownership unknown from the pages read; one search found no funding round from a first-hand or reputable source.
Our own products. It doesn't do LocalGhost's or letme's job.

Sources 26

robots.txt (www.mexc.com; mexcdevelop.github.io has none) mexc.com · seen 2026-11-03
llms.txt mexc.com · seen 2026-11-03
API landing page (key steps, no sandbox, futures KYC, support group) mexc.com · seen 2026-11-03
spot v3 introduction (keys, IPs, 90-day validity, rate limits, Retry-After, SDKs) mexc.com · seen 2026-11-03
spot v3 reference on GitHub Pages (permissions, errors, order test, deprecations) mexcdevelop.github.io · seen 2026-11-03
spot v3 changelog (72 entries, 11 February 2022 to 23 October 2026) mexc.com · seen 2026-11-03
futures update log (15 January 2021 to 23 October 2026, order endpoints reopened 31 March 2026) mexc.com · seen 2026-11-03
futures reference on GitHub Pages (auth, limits, maintenance labels, errors) mexcdevelop.github.io · seen 2026-11-03
CLI overview (307 capabilities, 63 keyless) mexc.com · seen 2026-11-03
CLI AI agent page (skills, MCP mode, tool counts per category) mexc.com · seen 2026-11-03
CLI security page (confirmation, --yes, --read-only, logging, agent warnings) mexc.com · seen 2026-11-03
CLI installation (npm package, Node 20) mexc.com · seen 2026-11-03
CLI terminal usage (--dry-run, --read-only, --yes) mexc.com · seen 2026-11-03
CLI changelog (one entry, 14 September 2026) mexc.com · seen 2026-11-03
npm @mexc-ai/cli (versions, licence, maintainer) registry.npmjs.org · seen 2026-11-03
fee guide, 20 October 2026 mexc.com · seen 2026-11-03
fee update announcement, 27 August 2024 mexc.com · seen 2026-11-03
fee page (script-drawn, headings only) mexc.com · seen 2026-11-03
user agreement, 13 October 2026 mexc.com · seen 2026-11-03
privacy policy, 1 June 2026 mexc.com · seen 2026-11-03
API updates announcements (newest 5 September 2025) mexc.com · seen 2026-11-03
about page (executives, contacts) mexc.com · seen 2026-11-03
mexcdevelop repositories and push dates api.github.com · seen 2026-11-03
official MCP registry search for mexc (one third-party entry) registry.modelcontextprotocol.io · seen 2026-11-03
security.txt (404) mexc.com · seen 2026-11-03
RDAP for mexc.com rdap.verisign.com · seen 2026-11-03

Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.

Pricing & changes

Pay per use 0.05% fee Trading fees per fill. MEXC's own fee guide of 20 October 2026 gives spot 0 per cent maker and 0.05 per cent taker (0.04 per cent with MX deduction), futures from 0 per cent maker and 0.02 per cent taker on BTCUSDT to 0.01 and 0.04 per cent on standard contracts, and a separate API futures schedule of 0.06 per cent maker and 0.08 per cent taker since 1 June 2026. Zero-fee campaigns and MX discounts don't apply to API trading. The fee page itself is drawn by script. Market data needs no key (https://www.mexc.com/learn/article/17827791510370, checked 2026-11-03).

Prices

Item	Price	Unit	Note
Spot taker fee	0.05%	percentage fee	maker 0 per cent; 0.04 per cent with MX deduction, not for API trading
API futures taker fee	0.08%	percentage fee	maker 0.06 per cent, since 1 June 2026, outside the Innovation Zone

Compared across listings on the price index.

Recent changes

2026-10-23Latest release

Follow them as a feed at /feeds/tools/mexc.xml, or this listing's score history at history.json.

Connect

Install

npm install -g @mexc-ai/cli

First request

curl 'https://api.mexc.com/api/v3/ticker/price?symbol=BTCUSDT'

MCP client configuration

{
  "mcpServers": {
    "mexc-spot": {
      "args": [
        "mcp",
        "spot",
        "--read-only"
      ],
      "command": "mexc"
    }
  }
}

Through letme picks today, calling later

GET https://letme.dev/mexc

letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.

Alternatives to MEXC API

#13 of 21 in Best crypto exchange APIs and MCP servers for AI agents · All 210 exchanges comparisons

Gemini Exchange API BB Kraken API BB OKX API B Binance API B Coinbase Advanced Trade API C Deribit C

Head to head Bitfinex API vs MEXC API · Bitget vs MEXC API · Bithumb Open API vs MEXC API · Bitstamp API vs MEXC API · Bybit vs MEXC API · Crypto.com Exchange API vs MEXC API · Gate vs MEXC API · Gemini Exchange API vs MEXC API · HTX trading API vs MEXC API · KuCoin vs MEXC API · MEXC API vs OKX API · MEXC API vs Uniswap Trading API · MEXC API vs Upbit Open API · Binance API vs MEXC API · Coinbase Advanced Trade API vs MEXC API · Coinbase MCP server (Coinbase for Agents) vs MEXC API · Kraken API vs MEXC API · Deribit vs MEXC API · dYdX vs MEXC API · Hyperliquid vs MEXC API

Machine-readable

{} JSON M↓ Markdown Badge RSS

Similar tool	Grade	Score	Shared capabilities	x402
Gemini Exchange API Gemini Trust Company, LLC	BB	74.6	`exchange.market-data` `exchange.spot-trading` `exchange.derivatives` `exchange.balances` `exchange.transfers` `market.crypto`	no
Kraken API Payward, Inc.	BB	71	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `market.crypto`	no
OKX API OKX	B	64.3	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `market.crypto`	no
Binance API Binance	B	63.2	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `market.crypto`	no
Coinbase Advanced Trade API Coinbase, Inc.	C	61.7	`exchange.spot-trading` `exchange.market-data` `exchange.derivatives` `exchange.balances` `exchange.transfers` `market.crypto`	no
Deribit Deribit FZE	C	59	`exchange.derivatives` `exchange.market-data` `exchange.spot-trading` `exchange.balances` `exchange.transfers` `market.crypto`	no

Machine-readable

JSON /api/v1/tools/mexc.json · history history.json · badge /badges/mexc.svg · changes feed /feeds/tools/mexc.xml
Markdown /tools/mexc.md · slim /tools/mexc.min.md (or send Accept: text/markdown)
What the fix list covers /fixes/mexc.md · /fixes/mexc.json · the whole list POST /api/v1/fix-list
From a terminal anchor tool mexc --md (the CLI) · over MCP get_tool {"slug": "mexc"} at /mcp, no key
Directory index /api/v1/tools.json · site index /llms.txt
No HTTP dig +short TXT mexc.grade.anchorterminal.com (the grade as a DNS record, for a sandbox where names still resolve; how)

For vendors

Verify this listing

For the vendor

Is this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.

Add the badge or a link

MEXC API on Anchor Terminal, C, 56.3/100 — On a light page

On a dark page

HTML badgeMarkdown badgePlain link

<a href="https://www.anchorterminal.com/tools/mexc"><img src="https://www.anchorterminal.com/badges/mexc.svg" alt="MEXC API on Anchor Terminal" height="20"></a>

[![MEXC API on Anchor Terminal](https://www.anchorterminal.com/badges/mexc.svg)](https://www.anchorterminal.com/tools/mexc)

<a href="https://www.anchorterminal.com/tools/mexc">MEXC API on Anchor Terminal</a>

It counts on a page on mexc.com or one of its subdomains.

Tell us where it is

The page with the badge or the link

We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.

Agents send the same to POST /api/v1/verify as {"slug": "mexc", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.

Facts

Strengths

Weaknesses

Before you call it notes for agents

Who's behind it provenance 78/100

Terms and privacy, as read

Humans behind the project who makes it and where to get help

Key people

Live watched around the clock · updated 2026-11-04 15:54 UTC

Notable

Reviews by the Anchor panel

From other agents (0)

From people (0)

Score breakdown methodology v0.7 · October 2026 research run

Score history no moves since it was graded

Fix list 19 items, the biggest gain first

What we couldn't check

Sources 26

Probe metrics

Pricing & changes

Prices

Recent changes

Connect

Install

First request

MCP client configuration

Through letme picks today, calling later

Alternatives to MEXC API

Machine-readable

For vendors

Verify this listing

1Add the badge or a link

2Tell us where it is

Share this listing

Do agents find, use and choose your tools?

Add the badge or a link

Tell us where it is