Kraken API vs MEXC API

Kraken API 67

Read with the hosted lines on the spot API. status.kraken.com is a Statuspage site with REST, WebSocket and FIX components (20). The incidents feed read covers 4 September to 3 November 2026. On 30 October spot and derivatives clients could not connect or submit orders across web, mobile, REST, WebSocket and FIX for 59 minutes 39 seconds, rated minor by Kraken; on 28 October some FIX clients were rejected on reconnection for 1 hour 59 minutes while other interfaces worked; the futures engine was degraded for 3 minutes on 13 October. A whole-exchange order outage 21 seconds short of an hour is read as one major (10 of 30). Numeric limits per key by tier and per pair for the matching engine (15). EAPI:Rate limit exceeded and EService:Throttled with a retry timestamp, a client order id and a validate flag on orders, but no Retry-After header (12 of 15). No SLA (0). Generally available (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.

MEXC API 43

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.

Kraken API 80

No OpenAPI file was found for the REST API in the docs read; the CLI's agents/tool-catalog.json gives JSON Schema inputs for all 188 commands and the 152 MCP tools (15 of 25). The docs serve Markdown twins such as quickstart.md and the CLI ships llms.txt, AGENTS.md and CONTEXT.md (10). Endpoint pages and guides on order lifecycle, errors and rate limits say what each call does, with less on when not to use one (15 of 20). Enums for order types, time in force and flags, and enums and required fields in the tool catalogue (12 of 15). Python, Node.js and cURL examples, an errors guide and the CLI's error-catalog.json with retry guidance (13 of 15). A changelog of 120 dated entries with deprecations dated (15). 15 + 10 + 15 + 12 + 13 + 15 = 80.

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.

Kraken API 79

The MCP server loads services with -s, defaults to no live trading, and its 152 tool definitions average about 520 characters; the REST API takes count, limit and pair filters but has no field selection (18 of 25). Cursor pagination on ledgers and trades since 30 September and 6 October 2026, with ofs deprecated (17 of 20). Prefixed error strings such as EOrder:Rate limit exceeded and EAPI:Invalid nonce, and the CLI's error catalogue says which to retry (17 of 20). cl_ord_id and validate on orders, destructive_hint and elicitation on dangerous MCP tools, no idempotency key on REST (16 of 20). An official Rust SDK at 5 stars, a Go module and example clients, HMAC-SHA512 signing with a strict nonce (11 of 15). 18 + 17 + 17 + 16 + 11 = 79.

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.

Kraken API 80

Keys with nine named permissions, optional expiry, IP restriction and nonce window, plus an OAuth sign-in from the CLI (authorisation code with PKCE, public client) that mints a no-withdrawal key expiring within 90 days or a read-only key (30). Read-only and no-withdrawal keys, position limits and pair allowlists in account settings, and MCP approval prompts for 33 dangerous tools (18 of 20). The API returns no untrusted content; the CLI docs warn that the feedback tool uploads a local file without approval (10). Keys and their permissions are listed in settings and ledgers record activity, but no per-call log for the operator was found (6 of 15). A valid security.txt, a bug bounty policy page, SECURITY.md and a secure SDLC workflow in the CLI; certifications not read (16 of 20). 30 + 18 + 10 + 6 + 16 = 80.

MEXC API 65

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.

Kraken API 40

No machine payment protocol (0). Maker and taker fees by tier published without login (20). Public market data, paper trading and the futures demo need no account or card (20). A person signs up, verifies and mints a key or approves the OAuth sign-in (0). 0 + 20 + 20 + 0 = 40.

MEXC API 31

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.

Kraken API 65

The editorial half. A closed service with clear terms naming regional Payward entities under California law; the CLI is MIT (15 of 30). The privacy notice was not read (5 of 30). The changelog dates deprecations and the terms carry a last-updated date (16 of 20). No subprocessor or data-location statement read (0 of 20). 15 + 5 + 16 + 0 = 36.

MEXC API 58

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.