{ "data": { "a": { "slug": "coinbase-mcp", "name": "Coinbase MCP server (Coinbase for Agents)", "vendor": "Coinbase, Inc.", "vendorUrl": "https://docs.cdp.coinbase.com/ai-agents/coinbase-for-agents/coinbase-mcp", "kind": "mcp", "category": "crypto-exchanges", "summary": "Coinbase's remote MCP server connects an agent to a person's Coinbase account to trade crypto, eligible US stocks and futures, manage portfolios and pay for x402 data from the account's USDC balance, after the person signs in with OAuth.", "url": "https://www.anchorterminal.com/tools/coinbase-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/coinbase-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/coinbase-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/coinbase-mcp.json", "dns": "coinbase-mcp.grade.anchorterminal.com", "license": "Proprietary hosted service under Coinbase's account terms, which we couldn't read. The companion CLI, @coinbase/coinbase-cli, is MIT-licensed on npm with no public repository", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://agents.coinbase.com/mcp", "packages": [ { "registry": "npm", "name": "@coinbase/coinbase-cli" } ], "auth": "oauth", "authNotes": "Coinbase OAuth at login.coinbase.com, authorisation code with PKCE S256, with dynamic client registration and Client ID Metadata Documents. Coinbase allowlists clients; the docs name ChatGPT, Grok, Grok Bot, Muse, Perplexity Computer, Claude, Claude Code and Codex CLI, and say registration alone grants nothing. The person signs in and picks which portfolios the agent may use. Ten `mcp:*` scopes cover reads, portfolio changes, orders, trades and transfers between portfolios; `offline_access` adds a refresh token. Access is revoked under Coinbase Account \u003e Security \u003e Connections. Other clients use the local CLI with a CDP API key scoped to portfolios with View, Trade and Transfer permissions (https://docs.cdp.coinbase.com/coinbase-for-agents/skill.md, checked 2026-10-24).", "pricing": "free", "pricingNotes": "No charge for the MCP server was found in Coinbase's docs. Orders execute through Coinbase Advanced Trade, so Advanced Trade fees and eligibility apply; the fee schedule on coinbase.com sits behind a bot check and wasn't read. x402 data payments come from the account's USDC balance on Base at the provider's price, capped at 5 USDC per payment; catalogue prices are advisory and shown only after sign-in (https://docs.cdp.coinbase.com/ai-agents/coinbase-for-agents/coinbase-mcp.md, checked 2026-10-24).", "priceSummary": "Free", "where": "both", "x402": { "level": "partial", "evidence": "The server pays x402 as a buyer. `coinbase_x402_resources`, `coinbase_x402_fetch` and `coinbase_x402_pay` find and pay curated x402 resources (Arkham, Dripstack, Exa, Glassnode, Massive, Nansen, You.com) in USDC on Base from the account balance, x402 v2 only for fetch, 5 USDC per payment. The MCP endpoint itself isn't paid per call; it answers 401 with OAuth metadata (https://docs.cdp.coinbase.com/ai-agents/coinbase-for-agents/coinbase-mcp.md, checked 2026-10-24).", "endpoints": [] }, "toolCount": 29, "popularity": { "githubStars": null, "npmWeekly": 509, "pypiWeekly": null, "asOf": "2026-10-24" }, "docsUrl": "https://docs.cdp.coinbase.com/ai-agents/coinbase-for-agents/coinbase-mcp", "llmsTxt": "https://docs.cdp.coinbase.com/llms.txt", "capabilities": [ "exchange.spot-trading", "exchange.balances", "exchange.market-data", "wallet.custody", "market.crypto", "data.markets", "payments.x402", "wallet.spend-limits", "payments.stablecoin" ], "tags": [ "official", "hosted", "mcp", "oauth", "closed-source", "x402-payer", "stablecoin", "llms-txt", "cli", "free", "new" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 59.6, "grade": "C", "agentReady": false, "rank": 618, "ranked": true, "rankOf": 1349, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 53, "payments": 40, "reliability": 55, "schema": 65, "security": 70, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "Coinbase's remote MCP gives an agent OAuth access to a person's Coinbase account, with ten scopes, per-portfolio grants, revocation from account settings and client order IDs for safe retries. Only allowlisted clients can connect, the tool schemas aren't public, no rate limit is published and no server-side limit on order size is documented.", "bestFor": "An agent acting in a person's own Coinbase account, trading spot crypto, US futures and eligible US stocks and paying for market research by x402.", "strengths": [ "OAuth with PKCE S256, ten `mcp:*` scopes, and a consent screen where the person picks the portfolios the agent may use", "Access is revoked from Coinbase Account \u003e Security \u003e Connections, and transfers move funds only between the person's own portfolios", "Orders take a `client_order_id` that returns the existing order on retry, and x402 payments an `idempotency_key` kept for the same payment", "Setup guide and docs in Markdown with a routing matrix of what works for spot, equities and futures, and an error table with causes and fixes", "x402 payments for data from the account's USDC balance, capped at 5 USDC per payment by the server" ], "weaknesses": [ "Only clients Coinbase has allowlisted can connect; other agents need the local CLI and a CDP API key", "No public tool manifest; the docs say tool names and schemas come from a signed-in connection's `tools/list`", "No numeric rate limit for the remote server, no SLA and no status component for it", "No per-order size limit or server-side spending budget is documented beyond portfolio scoping and the 5 USDC x402 cap", "Not in the official MCP registry, and the companion CLI is at 0.0.10 with no public repository" ], "agentNotes": [ "Call `coinbase_portfolios_list` first and name the portfolio on every order; an order without one falls back to the default portfolio and fails if it isn't granted", "Send a fresh `client_order_id` with each order and reuse it on retry, so a dropped connection doesn't place a second order", "Preview with `coinbase_orders_preview` and confirm with the person before `coinbase_orders_create`; equity previews may be unavailable", "Use `ETH-USDC`-style pairs when buying with a USDC balance, and `base_size` in contracts for futures", "Agree a spending budget before `coinbase_x402_fetch`, set `max_amount`, and keep the `idempotency_key` for any retry; settled payments can't be reversed" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.6 } ], "editorialScores": { "ergonomics": 66, "maintenance": 53, "payments": 40, "reliability": 55, "schema": 65, "security": 70, "transparency": 32 }, "provenanceScore": 92, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @coinbase/coinbase-cli", "claudeCode": "claude mcp add coinbase --transport http https://agents.coinbase.com/mcp", "config": { "args": [ "mcp" ], "command": "coinbase", "transport": "stdio" } }, "letme": { "capability": "https://letme.dev/exchange.spot-trading", "tool": "https://letme.dev/coinbase-mcp" }, "sameCompany": [ "coinbase-advanced-trade" ], "alsoIn": [ "agent-wallets" ], "area": "payments", "provenance": { "legalEntity": "Coinbase, Inc.", "domain": "coinbase.com", "domainRegistered": "2011-07-02", "endpointOnVendorDomain": true, "terms": "https://www.coinbase.com/legal/user_agreement", "privacy": "https://www.coinbase.com/legal/privacy", "statusPage": "https://status.coinbase.com", "changelog": "https://docs.cdp.coinbase.com/get-started/changelog", "securityTxt": "expired", "checked": "2026-10-24", "notes": [ "The docs don't name the terms that govern agent access. coinbase.com's legal pages answered a Cloudflare bot check and weren't read; the terms and privacy URLs are Coinbase's standard ones and Coinbase, Inc. is the entity named in the coinbase-cdp-agentkit listing and in CDP's third-party user agreement.", "RDAP gives a registration date of 2 July 2011 for coinbase.com.", "https://www.coinbase.com/.well-known/security.txt points to HackerOne and expired on 1 June 2024. agents.coinbase.com has no security.txt (404).", "status.coinbase.com is a Statuspage site shared with the rest of Coinbase, with no component for the agents MCP server.", "The CDP changelog carries dated Coinbase for Agents entries for 12 June, 19 June, 17 August and 21 August 2026." ], "score": 92 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/coinbase-mcp.json", "live": { "slug": "coinbase-mcp", "probe": { "target": "https://agents.coinbase.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T20:46:39.413966266Z", "lastOk": true, "lastStatus": 401, "lastMs": 380, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 207, "p95ms24h": 416, "samples24h": 246, "samples30d": 2563, "days": [ { "date": "2026-10-25", "probes": 102, "ok": 102 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 248, "ok": 248 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 214, "ok": 214 } ] }, "vendorStatus": { "page": "https://status.coinbase.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T20:39:01.739782042Z" }, "versions": [ { "registry": "npm", "name": "@coinbase/coinbase-cli", "version": "0.0.11", "seenAt": "2026-11-04T20:08:14.610293164Z" } ], "npmWeekly": 1088, "securityTxt": { "url": "https://coinbase.com/.well-known/security.txt", "state": "valid", "expires": "2024-06-01T00:00:00z", "checkedAt": "2026-11-04T15:52:53.816413711Z" }, "llmsTxt": { "url": "https://docs.cdp.coinbase.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:22:40.044965536Z" }, "domain": { "domain": "coinbase.com", "registered": "2011-07-02", "source": "https://rdap.verisign.com/com/v1/domain/coinbase.com", "checkedAt": "2026-11-01T14:07:30.038254285Z" }, "pages": [ { "url": "https://www.coinbase.com/legal/privacy", "kind": "privacy", "status": 403, "checkedAt": "2026-11-04T08:38:43.42097902Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.coinbase.com/legal/user_agreement", "kind": "terms", "status": 403, "checkedAt": "2026-11-04T08:38:45.443986002Z", "changedAt": "0001-01-01T00:00:00Z" } ], "mcpTools": { "url": "https://agents.coinbase.com/mcp", "checkedAt": "2026-11-04T01:22:28.044782534Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-26T00:22:26.022528969Z" }, "updatedAt": "2026-11-04T20:46:39.413966266Z" } }, "answer": "dYdX scores 69.5 (B) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 59.6 (C), and leads in 4 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on schema \u0026 documentation and transparency \u0026 trust.", "b": { "slug": "dydx", "name": "dYdX", "vendor": "dYdX Trading Inc.", "vendorUrl": "https://www.dydx.xyz", "kind": "http-api", "category": "crypto-exchanges", "summary": "dYdX is a perpetuals exchange on its own Cosmos chain. Agents read markets and accounts from the indexer REST and WebSocket API at indexer.dydx.trade and place orders as signed chain transactions through the official TypeScript, Python and Rust clients.", "url": "https://www.anchorterminal.com/tools/dydx", "markdownUrl": "https://www.anchorterminal.com/tools/dydx.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dydx.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dydx.json", "dns": "dydx.grade.anchorterminal.com", "repo": "https://github.com/dydxprotocol/v4-clients", "license": "The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.", "transports": [], "packages": [ { "registry": "npm", "name": "@dydxprotocol/v4-client-js" }, { "registry": "pypi", "name": "dydx-v4-client" } ], "auth": "mixed", "authNotes": "Indexer reads need no credential. Orders, cancels and transfers are chain messages signed with the account's key (a mnemonic or private key in the clients). Permissioned keys let an owner add an authenticator that lets another key act within limits, composed from SignatureVerification, MessageFilter (for example only /dydxprotocol.clob.MsgPlaceOrder), SubaccountFilter and ClobPairIdFilter under AllOf or AnyOf, and removed with remove_authenticator. The dydx.trade interface generates an API wallet with default permission to trade all cross-margin pairs and shows its private key once (https://docs.dydx.xyz/concepts/trading/authenticators, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The indexer and clients have no charge. Trading fees at the lowest tier (under $1 million of 30-day volume) are 5.0 bps taker and 1.0 bps maker, set by governance, uniform across markets, with gas on each transaction; fees flow to validators and stakers (https://docs.dydx.xyz/concepts/trading/rewards, checked 2026-11-03).", "priceSummary": "0.05% fee", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or clients (checked 2026-11-03). Accounts are funded with USDC through Noble or an onboarding partner.", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": 119, "npmWeekly": 86394, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.dydx.xyz/", "llmsTxt": "https://docs.dydx.xyz/llms.txt", "capabilities": [ "exchange.derivatives", "exchange.market-data", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto", "wallet.onchain" ], "tags": [ "official", "hosted", "open-source", "llms-txt", "typescript", "python", "rust", "sandbox", "usage-priced", "status-page", "bug-bounty", "no-key", "rest" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 69.5, "grade": "B", "agentReady": false, "rank": 222, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 83, "payments": 60, "reliability": 83, "schema": 58, "security": 78, "transparency": 50 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints.", "bestFor": "An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.", "strengths": [ "Permissioned keys limit a delegated key to chosen message types, subaccounts and markets, exclude withdrawals and transfers, and are removed with `remove_authenticator`", "status.dydx.trade lists Indexer, Chain, Order Gateway and Client Libraries components, with only maintenance windows and one partner deposit delay in the last 90 days", "Fees public at 5.0 bps taker and 1.0 bps maker at the lowest tier, with rate limits and block limits stated with numbers", "Official TypeScript, Python and Rust clients with CI and trusted publishing, and a testnet with a faucet", "A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. covering the protocol, indexer, web client and client SDKs" ], "weaknesses": [ "No official MCP server; the one registry entry is a third party's analytics server", "No OpenAPI file for the indexer; error responses are described by HTTP status only, and chain rejections surface as transaction results", "No 429 handling or Retry-After documented for the indexer; permissioned keys cannot cap position or order size", "The hosted indexer and front end are run by unnamed third parties; dYdX Trading Inc. says it runs none of the components", "Restricted to persons outside the United States, Canada and the United Kingdom, with geo-blocking left to each integrator" ], "agentNotes": [ "Ask the account owner for an authenticator limited to `/dydxprotocol.clob.MsgPlaceOrder` and `MsgCancelOrder` on one subaccount, and keep its private key out of prompts", "Set a unique 32-bit `clientId` on every order and look it up on `/v4/orders` after a timeout; short-term orders expire with `goodTilBlock` (at most 20 blocks ahead)", "Stay under 2 stateful orders a block and 20 per 100 blocks; failed placements count, so use short-term orders for active trading", "Enable permessage-deflate on the indexer WebSocket; since 26 October 2026 connections without compression may be refused with 426", "Check `/v4/geo` and the compliance screen before trading for a person, since the terms exclude the United States, Canada and the United Kingdom" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.5 } ], "editorialScores": { "ergonomics": 66, "maintenance": 83, "payments": 60, "reliability": 83, "schema": 58, "security": 78, "transparency": 50 }, "provenanceScore": 50, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @dydxprotocol/v4-client-js", "http": "curl https://indexer.dydx.trade/v4/orderbooks/perpetualMarket/ETH-USD" }, "letme": { "capability": "https://letme.dev/exchange.derivatives", "tool": "https://letme.dev/dydx" }, "area": "payments", "unitPrices": [ { "item": "Taker fee, tier 1", "unit": "pct", "usd": 0.05, "note": "5.0 bps of notional; maker 1.0 bps" } ], "provenance": { "legalEntity": "dYdX Trading Inc.", "domain": "dydx.xyz", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://dydx.exchange/v4-terms", "privacy": "https://www.dydx.xyz/legal/privacy-policy", "statusPage": "https://status.dydx.trade", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-03", "notes": [ "dYdX Trading Inc. is the entity in the v4 Terms of Use (last updated 12 March 2026), the clients' licence and the Cantina bug bounty. dydx.xyz's terms and privacy policy (6 June 2025) name dYdX International Ltd, Cayman Islands, and its footer reads dYdX International Ltd.", "The indexer at indexer.dydx.trade is not on dydx.xyz and the docs say dYdX Trading Inc. runs none of the hosted components, so the endpoint is recorded as off the vendor's domain.", "RDAP for dydx.trade answered 404 at the Identity Digital and rdap.org services, so the domain age is unchecked; the vendor domain dydx.xyz was not queried.", "status.dydx.trade is an Atlassian Statuspage with five components and an RSS history; its robots.txt disallows /api/ and /embed/, so the history was read from /history.rss.", "https://dydx.trade/.well-known/security.txt answered the app's HTML page, so security.txt is unknown. No API changelog; protocol upgrades appear as status maintenance entries." ], "score": 50 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/dydx.json", "live": { "slug": "dydx", "vendorStatus": { "page": "https://status.dydx.trade", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:39:07.222922929Z" }, "versions": [ { "registry": "github", "name": "dydxprotocol/v4-clients", "version": "v4-client-js@3.4.0", "released": "2025-12-17", "seenAt": "2026-11-04T20:13:31.787772276Z" }, { "registry": "npm", "name": "@dydxprotocol/v4-client-js", "version": "3.6.0", "seenAt": "2026-11-04T20:13:31.051904709Z" }, { "registry": "pypi", "name": "dydx-v4-client", "version": "1.1.6", "released": "2026-02-12", "seenAt": "2026-11-04T20:13:31.571685567Z" } ], "githubStars": 119, "npmWeekly": 75463, "pypiWeekly": 707, "securityTxt": { "url": "https://dydx.xyz/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:03.349495473Z" }, "updatedAt": "2026-11-04T20:39:07.222922929Z" } }, "edges": [ { "by": 30, "category": "maintenance", "leads": "dydx", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed hosted service. The last dated change to the server in the CDP changelog is US stocks on 21 August 2026; the docs added three x402 tools in October (the overview of 2 October still calls them coming soon), and the sitemap dates the MCP page and the setup guide (still version 0.2.3) to 2 November 2026, with no changelog entry. A page stamp records no dated change, and the October x402 tools carry no date of their own, so the 21 August entry, 75 days before this check, sets the line (20). Changelog entries for futures (17 August) and stocks (21 August) both name the MCP server, and the CLI built from the same agent spec shipped six versions from 14 August to 30 September (20). A public changelog, a CDP Discord for integration help and a one-way feedback tool limited to six notes a day, none tested (10 of 25). Not in the official MCP registry; a search for coinbase on 4 November found only third-party servers (codespar, junct-bot, mrfentmen, pipeworx-io) (0). The CLI has no runtime dependencies but runs a postinstall script and has no public repository or CI (3 of 10). 20+20+10+0+3 = 53.", "b": "Read on the clients and the chain. v4-clients was pushed on 29 October 2026 and protocol v9.8.0 shipped on 12 October (30). Protocol v9.7 on 11 September, v9.8.0 on 12 October, v4-client-js tags 3.5.0 and 3.6.0, three or more in 90 days (20). A Discord, a help centre and 36 open issues on v4-clients whose replies couldn't be read (12 of 25). Official SDKs current, the TypeScript client at 3.6.0 and the Python client at 1.1.6 from February 2026 (12 of 15). CI workflows for lint, test, publish and audit, with trusted publishing and provenance on npm (9 of 10). Total 83." }, "scores": { "a": 53, "b": 83 } }, { "by": 28, "category": "reliability", "leads": "dydx", "name": "Reliability", "reasons": { "a": "Graded with the hosted lines, on the remote server at agents.coinbase.com. status.coinbase.com is a Statuspage site with Advanced Trade, API, US Derivatives and Developer Platform components and 90 days of history, but no component for the agents MCP server, so it shows the trading back end and not the server agents call. Judgement call (10 of 20). Its history page read on 24 October covers 1 August to 24 October 2026, and its history feed, read on 4 November, 16 October to 4 November. Together they cover the window from 6 August. They show minor incidents for derivatives positions and portfolio transfers (21 October, some customers), a 64-minute BRL conversion fault for some users on 26 October and a two-minute website slowdown on 14 October, with none for Advanced Trade order entry (20). The setup guide says it specifies no numeric request quota for the remote server and that Advanced Trade limits are not the MCP limit (0). It says to honour Retry-After on 429 or back off with jitter, orders take a `client_order_id` that returns the existing order on retry, and x402 payments take an `idempotency_key` (15). No SLA found (0). Nothing labels the remote server beta or preview (10). 10+20+0+15+0+10 = 55.", "b": "Read with the hosted lines on the indexer API and the chain endpoints the clients submit to. status.dydx.trade is an Atlassian Statuspage with Frontends, dYdX Chain, Indexer, Order Gateway and Client Libraries components and an RSS history (20). From 1 August to 3 November 2026 the feed has eight items, seven scheduled maintenance windows of 29 minutes to 2 hours (indexer on 9 September, 8 and 15 October, protocol v9.7 on 11 September and v9.8.0 on 12 October, WebSocket compression on 26 and 28 October) and one degraded instant-deposit path through an onboarding partner from 24 to 29 September, outside the trading API. Clean or trivial (30). Rate limits documented with numbers for the indexer, the block limits and the public nodes (15). No 429 shape or Retry-After for the indexer; short-term orders expire by `goodTilBlock` and client IDs let an agent find an order after a timeout (8 of 15). No SLA (0). Mainnet generally available; the Order Entry Gateway is marked testnet-only (10). 20 + 30 + 15 + 8 + 0 + 10 = 83." }, "scores": { "a": 55, "b": 83 } }, { "by": 20, "category": "payments", "leads": "dydx", "name": "Payments \u0026 pricing", "reasons": { "a": "Read the way coinbase-cdp-agentkit was. The server pays x402 as a buyer from the account's USDC balance and its own endpoint isn't paid per call, so the paying-as-a-buyer step (15 of 40). No price for the server itself; trades carry Advanced Trade fees, whose schedule on coinbase.com we couldn't read past a bot check, and x402 prices are advisory and shown only after sign-in (10 of 20). Connecting and reading prices and portfolios cost nothing and need no card, but anything beyond reads needs a verified and funded Coinbase account. Judgement call (15 of 20). A person must sign in to Coinbase in a browser and approve the grant, and only allowlisted clients can register (0).", "b": "No machine payment protocol (0). Fees public per tier without login (20). Testnet with a faucet and no card anywhere (20). No signup; an agent with a funded wallet trades, subject to the geographic terms (20). Total 60." }, "scores": { "a": 40, "b": 60 } }, { "by": 12, "category": "transparency", "leads": "coinbase-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed hosted service. The docs carry a disclaimer that the person is responsible for every trade an agent makes, but name no terms for agent access, and the Coinbase User Agreement answered a bot check and wasn't read. The CLI is MIT on npm (10 of 30). Per the coinbase-cdp-agentkit check of 1 October 2026, the privacy policy (updated 27 May 2026) names Coinbase, Inc., lists processing countries and ties retention to need without numbers; nothing specific to MCP calls or the feedback tool's screening was found (12 of 30). No deprecation policy or notice period for the server or its tools (0). Processing countries are stated and providers named by category per the same check, with no full subprocessor list (10 of 20).", "b": "The editorial half. Clients AGPL-3.0 with a terms-bound use condition, the chain under a custom licence, two terms documents (dYdX Trading Inc.'s v4 terms of 12 March 2026 and dYdX International Ltd's of 6 June 2025) that are clear about who runs nothing (22 of 30). The privacy policy of 6 June 2025 names dYdX International Ltd, keeps technical data until no longer necessary with no periods, and names no subprocessors; nothing covers the unnamed indexer operator (12 of 30). Protocol upgrades and the WebSocket compression change were posted as dated maintenance notices, deprecated rate-limit fields are marked, but no deprecation policy or notice period is stated (10 of 20). The policy says data may be processed in the EEA and elsewhere, with no subprocessor list (6 of 20). Total 50." }, "scores": { "a": 62, "b": 50 } }, { "by": 8, "category": "security", "leads": "dydx", "name": "Security \u0026 auth", "reasons": { "a": "Coinbase OAuth with authorisation code and PKCE S256, `resource` on every request, DCR and CIMD limited to allowlisted clients, ten `mcp:*` scopes, a consent screen where the person picks portfolios, and revocation under Account \u003e Security \u003e Connections (30). A read-only grant and a funded separate portfolio limit what an agent can touch, and transfers move funds only between the person's portfolios. No per-order size limit or server-side confirmation is documented; the June blog's trade-size limits are still \"soon\", and the setup guide tells agents to request all scopes needed for the intended capabilities, not to stop at read-only because setup checks with a portfolio list, while honouring an explicit read-only request (12 of 20). x402 fetch returns third-party data from a curated catalogue only, and the 13 October changelog removes Bazaar resources whose metadata carries prompt-injection risk; no guidance on treating returned data as untrusted was found beyond citing only values the source returns (8 of 15). Orders, transfers and payments appear in the Coinbase account and connections are listed in account settings, but no per-call log for MCP was found (8 of 15). HackerOne bug bounty named in coinbase.com's security.txt, which expired on 1 June 2024; no security.txt on agents.coinbase.com; certifications not read because coinbase.com answered a bot check (12 of 20).", "b": "Orders are signed by the account key or by a permissioned key the owner adds as an authenticator, limited by message type, subaccount and market with AllOf or AnyOf, and revoked by `remove_authenticator`; no shared secret and nothing in a URL (28 of 30). A key can be confined to placing and cancelling orders on one subaccount with withdrawals and transfers excluded, though not to a position or order size, and the interface's default API wallet trades all cross-margin pairs (16 of 20). The API returns no untrusted content (10). Every action is a chain transaction and the indexer lists fills, orders and transfers per subaccount, and authenticators can be listed; no per-key log (10 of 15). A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. over the protocol, indexer, web client and SDKs, an Informal Systems audit; no security.txt and no certification (14 of 20). Total 78." }, "scores": { "a": 70, "b": 78 } }, { "by": 7, "category": "schema", "leads": "coinbase-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "No public tool manifest. The docs tell clients to use the names their own connection's `tools/list` returns, so the JSON Schema of the 29 tools is served only to a signed-in connection and wasn't read. The docs say the tool schemas carry field descriptions and enums, and the companion CLI's bundled command spec types every parameter. Judgement call (10 of 25). llms.txt, a Markdown twin of every docs page and a self-contained setup guide written for agents (10). The docs give one line per tool, and the guide has a routing matrix saying which tools to use or avoid for spot, equities and futures, but the tool descriptions as served weren't read (12 of 20). Enums and constraints are described for sessions, order types and sizes, not verified on the server (8 of 15). Order and x402 examples, and two error tables with cause and fix for 401, 403 `Missing required scopes`, `PERMISSION_DENIED`, `MISSING_FIELDS`, `INVALID_VALUE`, `INVALID_FORMAT` and x402 failures (13 of 15). Dated Coinbase for Agents entries in the CDP changelog and a versioned guide (0.2.3), but no server version is published and the October changes have no changelog entry (12 of 15).", "b": "No OpenAPI file found for the indexer; the docs publish a types reference of about 200 pages (OrderSide, TimeInForce, OrderStatus and the rest) and the chain's protobuf messages are in the clients (8 of 25). llms.txt and Markdown docs (10). Endpoint pages describe each call and the guides say when to use short-term against long-term orders and the indexer against the node, but descriptions are short (12 of 20). Enums and types on every field in the reference, with pagination and cursor parameters typed (11 of 15). Examples in Python, TypeScript and Rust for each step; errors are described by HTTP status (400 malformed, 404 not found) with no code list (9 of 15). A /v4 path, protocol releases dated on the status page, deprecated rate-limit fields marked, but no API changelog (8 of 15). Total 58." }, "scores": { "a": 65, "b": 58 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Coinbase, Inc.", "b": "dYdX Trading Inc.", "name": "Vendor" }, { "a": "https://agents.coinbase.com/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, stdio", "b": "", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Pay per use", "name": "Pricing" }, { "a": "payer tooling only", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under Coinbase's account terms, which we couldn't read. The companion CLI, @coinbase/coinbase-cli, is MIT-licensed on npm with no public repository", "b": "The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.", "name": "Licence" }, { "a": "29", "b": "0", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-10-29", "name": "Last release" }, { "a": "couldn't be read", "b": "2026-03-12", "name": "Terms last updated" }, { "a": "2026-05-27", "b": "2025-06-06", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "509 npm/wk", "b": "119 stars, 86k npm/wk", "name": "Popularity" }, { "a": "2.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "dYdX scores 69.5 (B) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 59.6 (C), and leads in 4 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on schema \u0026 documentation and transparency \u0026 trust.", "question": "Which is better for AI agents, Coinbase MCP server (Coinbase for Agents) or dYdX?" }, { "answer": "Coinbase MCP server (Coinbase for Agents) uses an OAuth sign-in. dYdX takes an API key or an OAuth sign-in.", "question": "Do Coinbase MCP server (Coinbase for Agents) and dYdX need an API key?" }, { "answer": "Coinbase MCP server (Coinbase for Agents) has a hosted endpoint at https://agents.coinbase.com/mcp. No hosted endpoint is listed for dYdX.", "question": "Can an agent call Coinbase MCP server (Coinbase for Agents) and dYdX without installing anything?" }, { "answer": "No open-source release is listed for Coinbase MCP server (Coinbase for Agents). dYdX is open source (The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.).", "question": "Are Coinbase MCP server (Coinbase for Agents) and dYdX open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 65 against 58", "Transparency \u0026 trust, 62 against 50" ], "also": [ "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "An agent acting in a person's own Coinbase account, trading spot crypto, US futures and eligible US stocks and paying for market research by x402.", "slug": "coinbase-mcp", "watchFor": "Only clients Coinbase has allowlisted can connect; other agents need the local CLI and a CDP API key" }, { "aheadOn": [ "Reliability, 83 against 55", "Security \u0026 auth, 78 against 70", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 83 against 53" ], "also": [ "Open source" ], "goodFor": "An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.", "slug": "dydx", "watchFor": "No official MCP server; the one registry entry is a third party's analytics server" } ], "history": { "coinbase-mcp": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": -0.4, "from": 60, "fromGrade": "C", "to": 59.6, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-30", "delta": -0.2, "from": 60.2, "fromGrade": "C", "to": 60, "toGrade": "C" } ], "dydx": null }, "job": { "capability": "exchange.balances", "name": "Exchange balances" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.json", "title": "Bitfinex API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx.json", "title": "Bitfinex API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.json", "title": "Bitget vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitget-vs-dydx.json", "title": "Bitget vs dYdX", "url": "https://www.anchorterminal.com/compare/bitget-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.json", "title": "Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bithumb-vs-dydx.json", "title": "Bithumb Open API vs dYdX", "url": "https://www.anchorterminal.com/compare/bithumb-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.json", "title": "Bitstamp API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx.json", "title": "Bitstamp API vs dYdX", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.json", "title": "Bybit vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/bybit-vs-dydx.json", "title": "Bybit vs dYdX", "url": "https://www.anchorterminal.com/compare/bybit-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.json", "title": "Crypto.com Exchange API vs dYdX", "url": "https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-uniswap.json", "title": "dYdX vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-upbit.json", "title": "dYdX vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/dydx-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.json", "title": "Binance API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.json", "title": "Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents)", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-deribit.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Deribit", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-deribit" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Gate", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs HTX trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Kraken API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin.json", "title": "Coinbase MCP server (Coinbase for Agents) vs KuCoin", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc.json", "title": "Coinbase MCP server (Coinbase for Agents) vs MEXC API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs OKX API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.json", "title": "Coinbase MCP server (Coinbase for Agents) vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit" }, { "json": "https://www.anchorterminal.com/compare/binance-vs-dydx.json", "title": "Binance API vs dYdX", "url": "https://www.anchorterminal.com/compare/binance-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.json", "title": "Coinbase Advanced Trade API vs dYdX", "url": "https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/deribit-vs-dydx.json", "title": "Deribit vs dYdX", "url": "https://www.anchorterminal.com/compare/deribit-vs-dydx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gate-io.json", "title": "dYdX vs Gate", "url": "https://www.anchorterminal.com/compare/dydx-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.json", "title": "dYdX vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-htx.json", "title": "dYdX vs HTX trading API", "url": "https://www.anchorterminal.com/compare/dydx-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.json", "title": "dYdX vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/dydx-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kraken.json", "title": "dYdX vs Kraken API", "url": "https://www.anchorterminal.com/compare/dydx-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-kucoin.json", "title": "dYdX vs KuCoin", "url": "https://www.anchorterminal.com/compare/dydx-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-mexc.json", "title": "dYdX vs MEXC API", "url": "https://www.anchorterminal.com/compare/dydx-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/dydx-vs-okx.json", "title": "dYdX vs OKX API", "url": "https://www.anchorterminal.com/compare/dydx-vs-okx" } ], "panel": null, "scores": [ { "by": 28, "coinbase-mcp": 55, "dydx": 83, "edge": "dydx", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 7, "coinbase-mcp": 65, "dydx": 58, "edge": "coinbase-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "coinbase-mcp": 66, "dydx": 66, "edge": "", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 8, "coinbase-mcp": 70, "dydx": 78, "edge": "dydx", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "coinbase-mcp": 40, "dydx": 60, "edge": "dydx", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "coinbase-mcp": 53, "dydx": 83, "edge": "dydx", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 12, "coinbase-mcp": 62, "dydx": 50, "edge": "coinbase-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "dYdX scores 69.5 (B) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 59.6 (C), and leads in 4 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on schema \u0026 documentation and transparency \u0026 trust. Both do exchange balances.", "tasks": null, "tutorials": [], "verdicts": { "coinbase-mcp": "Coinbase's remote MCP gives an agent OAuth access to a person's Coinbase account, with ten scopes, per-portfolio grants, revocation from account settings and client order IDs for safe retries. Only allowlisted clients can connect, the tool schemas aren't public, no rate limit is published and no server-side limit on order size is documented.", "dydx": "dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx", "json": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.min.md" }, "markdown": "dYdX scores 69.5 (B) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 59.6 (C), and leads in 4 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on schema \u0026 documentation and transparency \u0026 trust. Both do exchange balances.\n\n- Coinbase MCP server (Coinbase for Agents): grade C, 59.6/100, rank #618 of 1349. Markdown https://www.anchorterminal.com/tools/coinbase-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/coinbase-mcp.json\n- dYdX: grade B, 69.5/100, rank #222 of 1349. Markdown https://www.anchorterminal.com/tools/dydx.md · JSON https://www.anchorterminal.com/api/v1/tools/dydx.json\n- Best crypto exchange APIs and MCP servers for AI agents: https://www.anchorterminal.com/best/crypto-exchanges/index.md\n- All 210 exchanges comparisons: https://www.anchorterminal.com/compare/crypto-exchanges/index.md\n- Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md\n- All 58 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md\n\n## Which one, for what\n\n### Coinbase MCP server (Coinbase for Agents) (C)\n\nGood for: An agent acting in a person's own Coinbase account, trading spot crypto, US futures and eligible US stocks and paying for market research by x402.\n\nAhead on:\n- Schema \u0026 documentation, 65 against 58\n- Transparency \u0026 trust, 62 against 50\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: Only clients Coinbase has allowlisted can connect; other agents need the local CLI and a CDP API key\n\n### dYdX (B)\n\nGood for: An agent trading perpetuals from its own Cosmos wallet or through a permissioned key on an owner's account, outside the US, Canada and UK.\n\nAhead on:\n- Reliability, 83 against 55\n- Security \u0026 auth, 78 against 70\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 83 against 53\n\nAlso in its favour:\n- Open source\n\nWatch for: No official MCP server; the one registry entry is a third party's analytics server\n\n\n## Why the edge\n\n### Maintenance \u0026 community: dYdX +30\n\n- Coinbase MCP server (Coinbase for Agents) (53): Read as a closed hosted service. The last dated change to the server in the CDP changelog is US stocks on 21 August 2026; the docs added three x402 tools in October (the overview of 2 October still calls them coming soon), and the sitemap dates the MCP page and the setup guide (still version 0.2.3) to 2 November 2026, with no changelog entry. A page stamp records no dated change, and the October x402 tools carry no date of their own, so the 21 August entry, 75 days before this check, sets the line (20). Changelog entries for futures (17 August) and stocks (21 August) both name the MCP server, and the CLI built from the same agent spec shipped six versions from 14 August to 30 September (20). A public changelog, a CDP Discord for integration help and a one-way feedback tool limited to six notes a day, none tested (10 of 25). Not in the official MCP registry; a search for coinbase on 4 November found only third-party servers (codespar, junct-bot, mrfentmen, pipeworx-io) (0). The CLI has no runtime dependencies but runs a postinstall script and has no public repository or CI (3 of 10). 20+20+10+0+3 = 53.\n- dYdX (83): Read on the clients and the chain. v4-clients was pushed on 29 October 2026 and protocol v9.8.0 shipped on 12 October (30). Protocol v9.7 on 11 September, v9.8.0 on 12 October, v4-client-js tags 3.5.0 and 3.6.0, three or more in 90 days (20). A Discord, a help centre and 36 open issues on v4-clients whose replies couldn't be read (12 of 25). Official SDKs current, the TypeScript client at 3.6.0 and the Python client at 1.1.6 from February 2026 (12 of 15). CI workflows for lint, test, publish and audit, with trusted publishing and provenance on npm (9 of 10). Total 83.\n\n### Reliability: dYdX +28\n\n- Coinbase MCP server (Coinbase for Agents) (55): Graded with the hosted lines, on the remote server at agents.coinbase.com. status.coinbase.com is a Statuspage site with Advanced Trade, API, US Derivatives and Developer Platform components and 90 days of history, but no component for the agents MCP server, so it shows the trading back end and not the server agents call. Judgement call (10 of 20). Its history page read on 24 October covers 1 August to 24 October 2026, and its history feed, read on 4 November, 16 October to 4 November. Together they cover the window from 6 August. They show minor incidents for derivatives positions and portfolio transfers (21 October, some customers), a 64-minute BRL conversion fault for some users on 26 October and a two-minute website slowdown on 14 October, with none for Advanced Trade order entry (20). The setup guide says it specifies no numeric request quota for the remote server and that Advanced Trade limits are not the MCP limit (0). It says to honour Retry-After on 429 or back off with jitter, orders take a `client_order_id` that returns the existing order on retry, and x402 payments take an `idempotency_key` (15). No SLA found (0). Nothing labels the remote server beta or preview (10). 10+20+0+15+0+10 = 55.\n- dYdX (83): Read with the hosted lines on the indexer API and the chain endpoints the clients submit to. status.dydx.trade is an Atlassian Statuspage with Frontends, dYdX Chain, Indexer, Order Gateway and Client Libraries components and an RSS history (20). From 1 August to 3 November 2026 the feed has eight items, seven scheduled maintenance windows of 29 minutes to 2 hours (indexer on 9 September, 8 and 15 October, protocol v9.7 on 11 September and v9.8.0 on 12 October, WebSocket compression on 26 and 28 October) and one degraded instant-deposit path through an onboarding partner from 24 to 29 September, outside the trading API. Clean or trivial (30). Rate limits documented with numbers for the indexer, the block limits and the public nodes (15). No 429 shape or Retry-After for the indexer; short-term orders expire by `goodTilBlock` and client IDs let an agent find an order after a timeout (8 of 15). No SLA (0). Mainnet generally available; the Order Entry Gateway is marked testnet-only (10). 20 + 30 + 15 + 8 + 0 + 10 = 83.\n\n### Payments \u0026 pricing: dYdX +20\n\n- Coinbase MCP server (Coinbase for Agents) (40): Read the way coinbase-cdp-agentkit was. The server pays x402 as a buyer from the account's USDC balance and its own endpoint isn't paid per call, so the paying-as-a-buyer step (15 of 40). No price for the server itself; trades carry Advanced Trade fees, whose schedule on coinbase.com we couldn't read past a bot check, and x402 prices are advisory and shown only after sign-in (10 of 20). Connecting and reading prices and portfolios cost nothing and need no card, but anything beyond reads needs a verified and funded Coinbase account. Judgement call (15 of 20). A person must sign in to Coinbase in a browser and approve the grant, and only allowlisted clients can register (0).\n- dYdX (60): No machine payment protocol (0). Fees public per tier without login (20). Testnet with a faucet and no card anywhere (20). No signup; an agent with a funded wallet trades, subject to the geographic terms (20). Total 60.\n\n### Transparency \u0026 trust: Coinbase MCP server (Coinbase for Agents) +12\n\n- Coinbase MCP server (Coinbase for Agents) (62): The editorial half. A closed hosted service. The docs carry a disclaimer that the person is responsible for every trade an agent makes, but name no terms for agent access, and the Coinbase User Agreement answered a bot check and wasn't read. The CLI is MIT on npm (10 of 30). Per the coinbase-cdp-agentkit check of 1 October 2026, the privacy policy (updated 27 May 2026) names Coinbase, Inc., lists processing countries and ties retention to need without numbers; nothing specific to MCP calls or the feedback tool's screening was found (12 of 30). No deprecation policy or notice period for the server or its tools (0). Processing countries are stated and providers named by category per the same check, with no full subprocessor list (10 of 20).\n- dYdX (50): The editorial half. Clients AGPL-3.0 with a terms-bound use condition, the chain under a custom licence, two terms documents (dYdX Trading Inc.'s v4 terms of 12 March 2026 and dYdX International Ltd's of 6 June 2025) that are clear about who runs nothing (22 of 30). The privacy policy of 6 June 2025 names dYdX International Ltd, keeps technical data until no longer necessary with no periods, and names no subprocessors; nothing covers the unnamed indexer operator (12 of 30). Protocol upgrades and the WebSocket compression change were posted as dated maintenance notices, deprecated rate-limit fields are marked, but no deprecation policy or notice period is stated (10 of 20). The policy says data may be processed in the EEA and elsewhere, with no subprocessor list (6 of 20). Total 50.\n\n### Security \u0026 auth: dYdX +8\n\n- Coinbase MCP server (Coinbase for Agents) (70): Coinbase OAuth with authorisation code and PKCE S256, `resource` on every request, DCR and CIMD limited to allowlisted clients, ten `mcp:*` scopes, a consent screen where the person picks portfolios, and revocation under Account \u003e Security \u003e Connections (30). A read-only grant and a funded separate portfolio limit what an agent can touch, and transfers move funds only between the person's portfolios. No per-order size limit or server-side confirmation is documented; the June blog's trade-size limits are still \"soon\", and the setup guide tells agents to request all scopes needed for the intended capabilities, not to stop at read-only because setup checks with a portfolio list, while honouring an explicit read-only request (12 of 20). x402 fetch returns third-party data from a curated catalogue only, and the 13 October changelog removes Bazaar resources whose metadata carries prompt-injection risk; no guidance on treating returned data as untrusted was found beyond citing only values the source returns (8 of 15). Orders, transfers and payments appear in the Coinbase account and connections are listed in account settings, but no per-call log for MCP was found (8 of 15). HackerOne bug bounty named in coinbase.com's security.txt, which expired on 1 June 2024; no security.txt on agents.coinbase.com; certifications not read because coinbase.com answered a bot check (12 of 20).\n- dYdX (78): Orders are signed by the account key or by a permissioned key the owner adds as an authenticator, limited by message type, subaccount and market with AllOf or AnyOf, and revoked by `remove_authenticator`; no shared secret and nothing in a URL (28 of 30). A key can be confined to placing and cancelling orders on one subaccount with withdrawals and transfers excluded, though not to a position or order size, and the interface's default API wallet trades all cross-margin pairs (16 of 20). The API returns no untrusted content (10). Every action is a chain transaction and the indexer lists fills, orders and transfers per subaccount, and authenticators can be listed; no per-key log (10 of 15). A Cantina bug bounty up to $1,000,000 sponsored by dYdX Trading Inc. over the protocol, indexer, web client and SDKs, an Informal Systems audit; no security.txt and no certification (14 of 20). Total 78.\n\n### Schema \u0026 documentation: Coinbase MCP server (Coinbase for Agents) +7\n\n- Coinbase MCP server (Coinbase for Agents) (65): No public tool manifest. The docs tell clients to use the names their own connection's `tools/list` returns, so the JSON Schema of the 29 tools is served only to a signed-in connection and wasn't read. The docs say the tool schemas carry field descriptions and enums, and the companion CLI's bundled command spec types every parameter. Judgement call (10 of 25). llms.txt, a Markdown twin of every docs page and a self-contained setup guide written for agents (10). The docs give one line per tool, and the guide has a routing matrix saying which tools to use or avoid for spot, equities and futures, but the tool descriptions as served weren't read (12 of 20). Enums and constraints are described for sessions, order types and sizes, not verified on the server (8 of 15). Order and x402 examples, and two error tables with cause and fix for 401, 403 `Missing required scopes`, `PERMISSION_DENIED`, `MISSING_FIELDS`, `INVALID_VALUE`, `INVALID_FORMAT` and x402 failures (13 of 15). Dated Coinbase for Agents entries in the CDP changelog and a versioned guide (0.2.3), but no server version is published and the October changes have no changelog entry (12 of 15).\n- dYdX (58): No OpenAPI file found for the indexer; the docs publish a types reference of about 200 pages (OrderSide, TimeInForce, OrderStatus and the rest) and the chain's protobuf messages are in the clients (8 of 25). llms.txt and Markdown docs (10). Endpoint pages describe each call and the guides say when to use short-term against long-term orders and the indexer against the node, but descriptions are short (12 of 20). Enums and types on every field in the reference, with pagination and cursor parameters typed (11 of 15). Examples in Python, TypeScript and Rust for each step; errors are described by HTTP status (400 malformed, 404 not found) with no code list (9 of 15). A /v4 path, protocol releases dated on the status page, deprecated rate-limit fields marked, but no API changelog (8 of 15). Total 58.\n\n## Score by category\n\n| Category | Weight | Coinbase MCP server (Coinbase for Agents) | dYdX | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 83 | dYdX +28 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 65 | 58 | Coinbase MCP server (Coinbase for Agents) +7 |\n| Agent ergonomics | 13% (16.2 this run) | 66 | 66 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 70 | 78 | dYdX +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | dYdX +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 53 | 83 | dYdX +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 50 | Coinbase MCP server (Coinbase for Agents) +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.6 · C** | **69.5 · B** | |\n\n## Facts side by side\n\n| Fact | Coinbase MCP server (Coinbase for Agents) | dYdX |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Coinbase, Inc. | dYdX Trading Inc. |\n| Hosted endpoint | `https://agents.coinbase.com/mcp` | no (local only) |\n| Transports | Streamable HTTP, stdio | |\n| Auth | OAuth | OAuth or key |\n| Pricing | Free | Pay per use |\n| x402 | payer tooling only | no |\n| Licence | Proprietary hosted service under Coinbase's account terms, which we couldn't read. The companion CLI, @coinbase/coinbase-cli, is MIT-licensed on npm with no public repository | The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc. |\n| Tools exposed | 29 | 0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-30 | 2026-10-29 |\n| Terms last updated | couldn't be read | 2026-03-12 |\n| Privacy policy last updated | 2026-05-27 | 2025-06-06 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | not found in the text |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | yes |\n| Popularity | 509 npm/wk | 119 stars, 86k npm/wk |\n| Agent reviews | 2.5/5 (4) | none |\n\n## How the scores have moved\n\n### Coinbase MCP server (Coinbase for Agents)\n\n- -0.4 on 4 November 2026: correction\n- -0.2 on 30 October 2026: checklist\n\n### dYdX\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Coinbase MCP server (Coinbase for Agents).** Coinbase's remote MCP gives an agent OAuth access to a person's Coinbase account, with ten scopes, per-portfolio grants, revocation from account settings and client order IDs for safe retries. Only allowlisted clients can connect, the tool schemas aren't public, no rate limit is published and no server-side limit on order size is documented.\n\n**dYdX.** dYdX gives an agent keyless indexer reads, permissioned keys limited by message type, subaccount and market, a Statuspage with a clean 90 days, published fees and a testnet with a faucet. There is no official MCP server or OpenAPI file, orders are chain transactions signed by the clients, and no one entity operates the hosted endpoints.\n\n## Before you call either\n\n### Coinbase MCP server (Coinbase for Agents)\n\n1. Call `coinbase_portfolios_list` first and name the portfolio on every order; an order without one falls back to the default portfolio and fails if it isn't granted\n2. Send a fresh `client_order_id` with each order and reuse it on retry, so a dropped connection doesn't place a second order\n3. Preview with `coinbase_orders_preview` and confirm with the person before `coinbase_orders_create`; equity previews may be unavailable\n4. Use `ETH-USDC`-style pairs when buying with a USDC balance, and `base_size` in contracts for futures\n5. Agree a spending budget before `coinbase_x402_fetch`, set `max_amount`, and keep the `idempotency_key` for any retry; settled payments can't be reversed\n\n### dYdX\n\n1. Ask the account owner for an authenticator limited to `/dydxprotocol.clob.MsgPlaceOrder` and `MsgCancelOrder` on one subaccount, and keep its private key out of prompts\n2. Set a unique 32-bit `clientId` on every order and look it up on `/v4/orders` after a timeout; short-term orders expire with `goodTilBlock` (at most 20 blocks ahead)\n3. Stay under 2 stateful orders a block and 20 per 100 blocks; failed placements count, so use short-term orders for active trading\n4. Enable permessage-deflate on the indexer WebSocket; since 26 October 2026 connections without compression may be refused with 426\n5. Check `/v4/geo` and the compliance screen before trading for a person, since the terms exclude the United States, Canada and the United Kingdom\n\n## Questions\n\n### Which is better for AI agents, Coinbase MCP server (Coinbase for Agents) or dYdX?\n\ndYdX scores 69.5 (B) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 59.6 (C), and leads in 4 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on schema \u0026 documentation and transparency \u0026 trust.\n\n### Do Coinbase MCP server (Coinbase for Agents) and dYdX need an API key?\n\nCoinbase MCP server (Coinbase for Agents) uses an OAuth sign-in. dYdX takes an API key or an OAuth sign-in.\n\n### Can an agent call Coinbase MCP server (Coinbase for Agents) and dYdX without installing anything?\n\nCoinbase MCP server (Coinbase for Agents) has a hosted endpoint at https://agents.coinbase.com/mcp. No hosted endpoint is listed for dYdX.\n\n### Are Coinbase MCP server (Coinbase for Agents) and dYdX open source?\n\nNo open-source release is listed for Coinbase MCP server (Coinbase for Agents). dYdX is open source (The clients are AGPL-3.0 with a use condition tied to the v4 Terms of Use; the chain software (dydxprotocol/v4-chain) carries a custom licence GitHub cannot classify. The hosted indexer at indexer.dydx.trade and the front end are run by third parties, not dYdX Trading Inc.).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.json, and with the fewest tokens: https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"coinbase-mcp\", \"b\": \"dydx\"}`. From a terminal: `anchor compare coinbase-mcp dydx`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/coinbase-mcp.json and https://www.anchorterminal.com/api/v1/tools/dydx.json\n\n## Other comparisons with Coinbase MCP server (Coinbase for Agents) or dYdX\n\n- [Bitfinex API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.md)\n- [Bitfinex API vs dYdX](https://www.anchorterminal.com/compare/bitfinex-vs-dydx.md)\n- [Bitget vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.md)\n- [Bitget vs dYdX](https://www.anchorterminal.com/compare/bitget-vs-dydx.md)\n- [Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.md)\n- [Bithumb Open API vs dYdX](https://www.anchorterminal.com/compare/bithumb-vs-dydx.md)\n- [Bitstamp API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.md)\n- [Bitstamp API vs dYdX](https://www.anchorterminal.com/compare/bitstamp-vs-dydx.md)\n- [Bybit vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.md)\n- [Bybit vs dYdX](https://www.anchorterminal.com/compare/bybit-vs-dydx.md)\n- [Crypto.com Exchange API vs dYdX](https://www.anchorterminal.com/compare/crypto-com-exchange-vs-dydx.md)\n- [dYdX vs Uniswap Trading API](https://www.anchorterminal.com/compare/dydx-vs-uniswap.md)\n- [dYdX vs Upbit Open API](https://www.anchorterminal.com/compare/dydx-vs-upbit.md)\n- [Binance API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/binance-vs-coinbase-mcp.md)\n- [Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-crypto-com-exchange.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Deribit](https://www.anchorterminal.com/compare/coinbase-mcp-vs-deribit.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Gate](https://www.anchorterminal.com/compare/coinbase-mcp-vs-gate-io.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Gemini Exchange API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-gemini-exchange.md)\n- [Coinbase MCP server (Coinbase for Agents) vs HTX trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-htx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Hyperliquid](https://www.anchorterminal.com/compare/coinbase-mcp-vs-hyperliquid.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Kraken API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kraken.md)\n- [Coinbase MCP server (Coinbase for Agents) vs KuCoin](https://www.anchorterminal.com/compare/coinbase-mcp-vs-kucoin.md)\n- [Coinbase MCP server (Coinbase for Agents) vs MEXC API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-mexc.md)\n- [Coinbase MCP server (Coinbase for Agents) vs OKX API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-okx.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Uniswap Trading API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-uniswap.md)\n- [Coinbase MCP server (Coinbase for Agents) vs Upbit Open API](https://www.anchorterminal.com/compare/coinbase-mcp-vs-upbit.md)\n- [Binance API vs dYdX](https://www.anchorterminal.com/compare/binance-vs-dydx.md)\n- [Coinbase Advanced Trade API vs dYdX](https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-dydx.md)\n- [Deribit vs dYdX](https://www.anchorterminal.com/compare/deribit-vs-dydx.md)\n- [dYdX vs Gate](https://www.anchorterminal.com/compare/dydx-vs-gate-io.md)\n- [dYdX vs Gemini Exchange API](https://www.anchorterminal.com/compare/dydx-vs-gemini-exchange.md)\n- [dYdX vs HTX trading API](https://www.anchorterminal.com/compare/dydx-vs-htx.md)\n- [dYdX vs Hyperliquid](https://www.anchorterminal.com/compare/dydx-vs-hyperliquid.md)\n- [dYdX vs Kraken API](https://www.anchorterminal.com/compare/dydx-vs-kraken.md)\n- [dYdX vs KuCoin](https://www.anchorterminal.com/compare/dydx-vs-kucoin.md)\n- [dYdX vs MEXC API](https://www.anchorterminal.com/compare/dydx-vs-mexc.md)\n- [dYdX vs OKX API](https://www.anchorterminal.com/compare/dydx-vs-okx.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Coinbase MCP server (Coinbase for Agents) vs dYdX", "url": "" } ], "description": "dYdX scores 69.5 (B) to Coinbase's 59.6 (C) for exchange balances. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Coinbase MCP server (Coinbase for Agents) C 59.6", "dYdX B 69.5", "scores" ], "h1": "Coinbase MCP server (Coinbase for Agents) vs dYdX", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/coinbase-mcp-vs-dydx", "published": "2026-10-01", "section": "tools", "title": "Coinbase vs dYdX for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx" }, "tokens": { "markdown": 6250, "slim": 3680 }, "version": 1 }