Head to head · Exchange market data · October 2026 research run

Bitpont API and MCP vs MEXC API

Bitpont API and MCP scores 62.9 (B) on agent readiness against MEXC API's 58.3 (C), and leads in 4 of 7 scored categories. MEXC API leads on maintenance & community. Both do exchange market data.

Best crypto exchange APIs and MCP servers for AI agents · All 231 exchanges comparisons

Which one, for what

Bitpont API and MCP B

Best for An aggregator over DeFi venues (Jupiter, KyberSwap, LI.FI, deBridge, Aave, Morpho, Hyperliquid, GMX, Derive) rather than an exchange with its own order book.

Ahead on

  • Schema & documentation, 82 against 64
  • Agent ergonomics, 74 against 64
  • Payments & pricing, 90 against 47

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

No status page, no SLA and no sandbox or testnet in the reviewed documentation

MEXC API C

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

Ahead on

  • Maintenance & community, 75 against 14

Also in its favour

  • Runs on your own machine

Watch for

No sandbox or testnet; only an order-validation endpoint

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community MEXC API +61

Bitpont API and MCP 14

Read as a closed hosted service. The changelog names versions (Bitpont 5.102.20, API 1.9) with no dates, so the time since the last release can't be established (0) and there are no dated entries (0). A public changelog and a support email; no answer observed and the GitHub organisation is closed to our reader (6 of 15). A first-party JavaScript client and TypeScript declarations as downloads, not on a package registry, and no MCP registry entry (8 of 15). No package or public CI seen (0). The public announcement was on 20 November 2026, so the record is days old. Total 14.

MEXC API 75

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.

Payments & pricing Bitpont API and MCP +43

Bitpont API and MCP 90

No x402, MPP or L402; a verified trading fee lifting quotas for an hour is not a payment protocol (0). The API is free under published limits and the 0.40% interface fee is published per route without a login (30). Free access with no card (30). An agent starts with no signup by creating a private workspace through the API (30). Total 90.

MEXC API 47

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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 31 is 47.

Schema & documentation Bitpont API and MCP +18

Bitpont API and MCP 82

OpenAPI 3.1 file Bitpont Developer API 1.33.0 with 1,149 operations, read once as the reference viewer's source (25). llms.txt, Markdown downloads of the developer pages and Markdown agent guides (10). Every operation has a description and most a summary that states its job, and the guides say which tool to use for which task, though few say when not to (14 of 20). Enums, regex patterns and length limits on addresses and base-unit amounts, required fields; some inputs still allow free-form objects and the MCP operation takes a generic params object (12 of 15). Code examples in the guides and a shared error schema with code, requestId and retryable on 400 to 504 (13 of 15). A versioned changelog, but its entries carry no dates and its latest API version (1.9) doesn't match the file's 1.33.0 (8 of 15). Total 82.

MEXC API 64

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 ergonomics Bitpont API and MCP +10

Bitpont API and MCP 74

Read for the hosted MCP server, whose catalogue has 1,148 tools (5), with 10 added back for ?product= profiles, bitpont_findTools and bitpont_describeTool and paginated tools/list (15 of 25). Cursors, limits, product and network filters and read batches (18 of 20). Errors carry code, retryable and requestId, and checkInputs returns JSON Pointer paths before any provider is called (19 of 20). Idempotent tasks and stable request IDs, with a documented rule never to repeat an unknown submission; readOnlyHint and destructiveHint unchecked because tools/list was not sent, and the catalogue carries no annotations (14 of 20). A JavaScript client with TypeScript declarations, OpenAI function definitions and a Postman collection, one language (8 of 15). Total 74.

MEXC API 64

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.

Score by category

CategoryWeightBitpont API and MCPMEXC APIEdge
Reliability16%4543Bitpont API and MCP +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8264Bitpont API and MCP +18
Agent ergonomics13%7464Bitpont API and MCP +10
Security & auth14%6365MEXC API +2
Payments & pricing10%9047Bitpont API and MCP +43
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%1475MEXC API +61
Transparency & trust7%5858even
Negative events≤1500
TotalB 62.9/100C 58.3/100

Facts side by side

FactBitpont API and MCPMEXC API
KindHTTP APIHTTP API
VendorBitpont (LiMiT)MEXC (Comoros) Ltd
Hosted endpointhttps://www.bitpont.com/api/v1/mcpno (local only)
TransportsStreamable HTTPstdio
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceA proprietary hosted service under the Bitpont Terms of Use (LIMIT SRL). The terms licence the published SDK, declarations, examples and API documentation for building integrations, with no copyright fee; the backend is closednone
Tools exposed1148299
Read-only variant documentednoyes
llms.txtyesyes
Last releasenone2026-10-23
Terms last updatedno date given2026-10-13
Privacy policy last updated2026-11-112026-06-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularitynone315 stars

How the scores have moved

Verdicts

Bitpont API and MCP

Public market reads, quotes and unsigned transaction drafts work without an account, every trade is signed in the owner's wallet, and an OpenAPI 3.1 file covers all 1,148 operations. There is no status page, the changelog carries no dates, and the hosted MCP server exposes the same 1,148 tools, narrowed by product filters and a search tool.

MEXC API

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.

Before you call either

Bitpont API and MCP

  1. Connect with ?product=swap or another product ID, then call bitpont_findTools and bitpont_describeTool rather than loading all 1,148 tools
  2. Create a private workspace before the first ticket and store its secret and your requestId; reuse both to recover an order
  3. Call bitpont_checkInputs before preparing a transaction; amounts are base-unit decimal strings
  4. If a request returns 429, wait for the Retry-After value. The free budget is 30 units a minute per IP and a batch costs one unit per item
  5. Never repeat a submission whose outcome is unknown; read the execution receipt first

MEXC API

  1. 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
  2. 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
  3. Call POST /api/v3/order/test before a live order, since there is no sandbox
  4. 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
  5. Treat a 5xx on an order as unknown, not failed, and query the order before retrying; set newClientOrderId so the order can be found

Questions

Which is better for AI agents, Bitpont API and MCP or MEXC API?

Bitpont API and MCP scores 62.9 (B) on agent readiness against MEXC API's 58.3 (C), and leads in 4 of 7 scored categories. MEXC API leads on maintenance & community.

Do Bitpont API and MCP and MEXC API need an API key?

Bitpont API and MCP takes an API key or an OAuth sign-in. MEXC API needs an API key.

Can an agent call Bitpont API and MCP and MEXC API without installing anything?

Bitpont API and MCP has a hosted endpoint at https://www.bitpont.com/api/v1/mcp. MEXC API runs on your own machine, with no hosted endpoint listed.

Other comparisons with Bitpont API and MCP or MEXC API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.