{ "data": { "a": { "slug": "bitstamp", "name": "Bitstamp API", "vendor": "Bitstamp Ltd.", "vendorUrl": "https://www.bitstamp.net", "kind": "http-api", "category": "crypto-exchanges", "summary": "Bitstamp's HTTP API v2 for spot and derivatives trading, balances, deposits and withdrawals, with WebSocket and FIX feeds and a sandbox at sandbox.bitstamp.net. Bitstamp is a Robinhood company since June 2025.", "url": "https://www.anchorterminal.com/tools/bitstamp", "markdownUrl": "https://www.anchorterminal.com/tools/bitstamp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bitstamp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bitstamp.json", "dns": "bitstamp.grade.anchorterminal.com", "license": "Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load", "transports": [], "packages": [], "auth": "api-key", "authNotes": "API key and secret made in the Bitstamp account after a browser signup, sent as `X-Auth: BITSTAMP {key}` with an HMAC-SHA256 `X-Auth-Signature` over the verb, host, path, query, nonce, timestamp and body, a 36-character single-use nonce and a timestamp within 150 seconds. Keys carry per-endpoint permissions (error API0003 names a missing permission) and an IP allow-list (API0002), and `X-Auth-Subaccount-Id` targets a sub-account. `POST /api/v2/revoke_all_api_keys/` is a kill switch for every key. Responses carry an `X-Server-Auth-Signature` to verify (https://www.bitstamp.net/api/, checked 2026-11-03).", "pricing": "usage", "pricingNotes": "The API itself costs nothing. Trading fees are maker and taker by 30-day volume per the API's fees endpoints, but the fee schedule page at bitstamp.net/fee-schedule/ draws its table by script and loaded empty for our reader, so the rates are unchecked. Commercial use of exchange data needs a Data License Agreement through partners@bitstamp.net. The sandbox at sandbox.bitstamp.net needs no money (https://www.bitstamp.net/api/, checked 2026-11-03).", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation (checked 2026-11-03). Fees are taken from the account; onboarding is a browser signup.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.bitstamp.net/api/", "capabilities": [ "exchange.market-data", "exchange.spot-trading", "exchange.derivatives", "exchange.balances", "exchange.transfers", "exchange.staking", "market.crypto" ], "tags": [ "official", "hosted", "api-key", "sandbox", "status-page", "usage-priced", "eu", "uk" ], "lastRelease": "2026-08-28", "graded": true, "anchor": { "graded": true, "score": 50.4, "grade": "D", "agentReady": false, "rank": 948, "ranked": true, "rankOf": 1349, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 58, "maintenance": 28, "payments": 20, "reliability": 63, "schema": 51, "security": 60, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.", "bestFor": "An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing.", "strengths": [ "Rate limits with numbers (400 requests a second, 10,000 per 10 minutes) and named error codes for client and market limits", "Keys carry per-endpoint permissions and an IP allow-list, and one call revokes every key on the account", "A sandbox at sandbox.bitstamp.net with the same v2 paths, plus order-data endpoints to recover gaps after a dropped WebSocket", "A dated API changelog from 2023 to 28 August 2026 and a Statuspage feed with per-market incidents", "Signed responses (`X-Server-Auth-Signature`) let a client verify what the server returned" ], "weaknesses": [ "No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data", "Duplicate client order ids are allowed since November 2023, so a retried order can execute twice", "The fee schedule, terms of use, privacy policy, about page and FAQ load empty without a browser, so fees, retention and the bot clauses are unchecked", "A 3-hour withdrawal failure across 14 networks on 21 August 2026 and a 39-minute halt of all markets on 5 August 2026", "security.txt expired on 12 July 2026, and no SLA was found" ], "agentNotes": [ "Mint a key with only the endpoint permissions the task needs and an IP allow-list; keep `revoke_all_api_keys` in reach as a kill switch", "Treat `client_order_id` as a label, not a guard. On a timeout (500.016) fetch the order by client id before resending, because duplicates are accepted", "Use a fresh 36-character nonce and a timestamp within 150 seconds of server time on every request, or expect API0004 and API0017", "Stay under 400 requests a second and 10,000 per 10 minutes; 400.002 and 400.067 mean back off, and open-orders answers are cached for 10 seconds", "Start on sandbox.bitstamp.net with the same paths, and read the fee schedule in a browser before quoting costs, since it is unreadable to a plain fetch" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.4 } ], "editorialScores": { "ergonomics": 58, "maintenance": 28, "payments": 20, "reliability": 63, "schema": 51, "security": 60, "transparency": 16 }, "provenanceScore": 90, "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": { "http": "curl https://www.bitstamp.net/api/v2/ticker/btcusd/" }, "letme": { "capability": "https://letme.dev/exchange.market-data", "tool": "https://letme.dev/bitstamp" }, "area": "payments", "provenance": { "legalEntity": "Bitstamp Ltd.", "domain": "bitstamp.net", "domainRegistered": "2011-07-04", "endpointOnVendorDomain": true, "terms": "https://www.bitstamp.net/terms-of-use/", "privacy": "https://www.bitstamp.net/privacy-policy/", "statusPage": "https://status.bitstamp.net", "changelog": "https://www.bitstamp.net/api/", "securityTxt": "expired", "checked": "2026-11-03", "notes": [ "Bitstamp Ltd. is named in Robinhood's newsroom post of 2 June 2025 on closing the acquisition; the terms of use and privacy policy pages loaded empty for our reader, so the entities they name are unconfirmed.", "RDAP gives bitstamp.net a registration date of 4 July 2011.", "https://www.bitstamp.net/.well-known/security.txt names HackerOne's Robinhood programme as Contact and Policy and expired on 12 July 2026.", "www.bitstamp.net/robots.txt allows /api/ itself and disallows /api/*, /account/, /trade/ and others; only /api/ was read under it. status.bitstamp.net disallows /api/ and /embed/, so the history feed was read. support.bitstamp.net did not resolve.", "The API changelog is a section of the API documentation page; there is no separate changelog URL." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/bitstamp.json", "live": { "slug": "bitstamp", "vendorStatus": { "page": "https://status.bitstamp.net", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-11-04T20:38:43.0107081Z" }, "securityTxt": { "url": "https://bitstamp.net/.well-known/security.txt", "state": "expired", "expires": "2026-07-12T11:59:00.000Z", "checkedAt": "2026-11-04T15:53:31.314157297Z" }, "updatedAt": "2026-11-04T20:38:43.0107081Z" } }, "answer": "Coinbase MCP server (Coinbase for Agents) scores 59.6 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 6 of 7 scored categories. Bitstamp API leads on reliability.", "b": { "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" } }, "edges": [ { "by": 25, "category": "maintenance", "leads": "coinbase-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The last dated API change is 28 August 2026, 67 days before the check (20). Only one dated entry in the last 90 days, after 1 July and 12 June (0). No public repository or issue tracker, support pages did not load and support.bitstamp.net did not resolve; a changelog exists (8 of 25). No official SDKs and no MCP registry presence of Bitstamp's own (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28.", "b": "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." }, "scores": { "a": 28, "b": 53 } }, { "by": 20, "category": "payments", "leads": "coinbase-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). The fee schedule page loaded empty, the API's fee endpoints need a key, and no rate could be read, so fees are scored as not published (0, unchecked). The API is free, public endpoints need no key and the sandbox needs no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 0 + 20 + 0 = 20.", "b": "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)." }, "scores": { "a": 20, "b": 40 } }, { "by": 14, "category": "schema", "leads": "coinbase-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI or other machine-readable contract was found on the API page or elsewhere (0). No llms.txt or Markdown docs (0). The single documentation page describes each endpoint's purpose and parameters, with notes such as the 10-second cache on open orders and the Travel Rule fields, but not when to use one endpoint over another (14 of 20). Parameters are typed with enumerations (margin mode CROSS or ISOLATED, margin multiplier 1 to 25, order types) and required fields marked (11 of 15). Signing examples in Python, Java and C++, and error families with numbered codes and explanations (13 of 15). Version v2 in the path and header, a dated changelog from 7 April 2023 to 28 August 2026, and a 410.001 code for deprecated endpoints, with no stated notice period (13 of 15). 0 + 0 + 14 + 11 + 13 + 13 = 51.", "b": "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)." }, "scores": { "a": 51, "b": 65 } }, { "by": 10, "category": "security", "leads": "coinbase-mcp", "name": "Security \u0026 auth", "reasons": { "a": "Revocable HMAC-SHA256 keys with per-endpoint permissions, an IP allow-list, single-use nonces, a timestamp window, sub-account scoping and a one-call kill switch for every key; no key expiry found (24 of 30). Permissions are chosen per endpoint and withdrawals can need Travel Rule address verification, but whether a withdrawal address allow-list exists sits in the unread account settings and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). No per-key audit log found; the account's transaction history is the record (4 of 15). security.txt names HackerOne's Robinhood programme but expired on 12 July 2026; no certification page was readable (8 of 20). 24 + 14 + 10 + 4 + 8 = 60.", "b": "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)." }, "scores": { "a": 60, "b": 70 } }, { "by": 9, "category": "transparency", "leads": "coinbase-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. A closed service whose terms of use loaded empty for our reader, so the licence and clauses are unknown (8 of 30). The privacy policy loaded empty, so retention and data handling are unchecked (0 of 30). A 410.001 code marks deprecated endpoints and the changelog records replacements such as `trading-pairs-info` by `markets`, with no notice period stated (8 of 20). Subprocessors and data locations are in the unread privacy policy (0). 8 + 0 + 8 + 0 = 16.", "b": "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)." }, "scores": { "a": 53, "b": 62 } }, { "by": 8, "category": "reliability", "leads": "bitstamp", "name": "Reliability", "reasons": { "a": "Read with the hosted lines on the HTTP API v2 at www.bitstamp.net/api/v2/. status.bitstamp.net is a Statuspage site with component history (20). Its feed for 5 August to 3 November 2026 has 17 entries, among them withdrawals failing on 14 networks for about 3 hours on 21 August, database maintenance with login failures and intermittent trading interruptions for about 1 hour 44 minutes on 23 September, a 39-minute halt of all markets on 5 August, and delistings and single-asset suspensions. One major (10). Rate limits with numbers, 400 a second and 10,000 per 10 minutes (15). Limit errors are named (400.002, 400.067, 400.068) but there is no Retry-After or backoff guidance, duplicate client order ids are allowed, and the only retry guidance is to check the order after a 500.016 timeout (8 of 15). No SLA found (0). Generally available (10). 20 + 10 + 15 + 8 + 0 + 10 = 63.", "b": "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." }, "scores": { "a": 63, "b": 55 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "Bitstamp Ltd.", "b": "Coinbase, Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://agents.coinbase.com/mcp", "name": "Hosted endpoint" }, { "a": "", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "payer tooling only", "name": "x402" }, { "a": "Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load", "b": "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", "name": "Licence" }, { "a": "none", "b": "29", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-28", "b": "2026-09-30", "name": "Last release" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-05-27", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "509 npm/wk", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Coinbase MCP server (Coinbase for Agents) scores 59.6 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 6 of 7 scored categories. Bitstamp API leads on reliability.", "question": "Which is better for AI agents, Bitstamp API or Coinbase MCP server (Coinbase for Agents)?" }, { "answer": "Bitstamp API needs an API key. Coinbase MCP server (Coinbase for Agents) uses an OAuth sign-in.", "question": "Do Bitstamp API and Coinbase MCP server (Coinbase for Agents) need an API key?" }, { "answer": "No hosted endpoint is listed for Bitstamp API. Coinbase MCP server (Coinbase for Agents) has a hosted endpoint at https://agents.coinbase.com/mcp.", "question": "Can an agent call Bitstamp API and Coinbase MCP server (Coinbase for Agents) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 55" ], "also": null, "goodFor": "An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing.", "slug": "bitstamp", "watchFor": "No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data" }, { "aheadOn": [ "Schema \u0026 documentation, 65 against 51", "Agent ergonomics, 66 against 58", "Security \u0026 auth, 70 against 60", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 53 against 28", "Transparency \u0026 trust, 62 against 53" ], "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" } ], "history": { "bitstamp": null, "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" } ] }, "job": { "capability": "exchange.market-data", "name": "Exchange market data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.json", "title": "Bitfinex API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp" }, { "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/bitget-vs-bitstamp.json", "title": "Bitget vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bitget-vs-bitstamp" }, { "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/bithumb-vs-bitstamp.json", "title": "Bithumb Open API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/bithumb-vs-bitstamp" }, { "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/bitstamp-vs-bybit.json", "title": "Bitstamp API vs Bybit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-bybit" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.json", "title": "Bitstamp API vs Coinbase Advanced Trade API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.json", "title": "Bitstamp API vs Crypto.com Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit.json", "title": "Bitstamp API vs Deribit", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-deribit" }, { "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/bitstamp-vs-gate-io.json", "title": "Bitstamp API vs Gate", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gate-io" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.json", "title": "Bitstamp API vs Gemini Exchange API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-htx.json", "title": "Bitstamp API vs HTX trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-htx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.json", "title": "Bitstamp API vs Hyperliquid", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken.json", "title": "Bitstamp API vs Kraken API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kraken" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.json", "title": "Bitstamp API vs KuCoin", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-kucoin" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc.json", "title": "Bitstamp API vs MEXC API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-mexc" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-okx.json", "title": "Bitstamp API vs OKX API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-okx" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.json", "title": "Bitstamp API vs Uniswap Trading API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-uniswap" }, { "json": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit.json", "title": "Bitstamp API vs Upbit Open API", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-upbit" }, { "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/binance-vs-bitstamp.json", "title": "Binance API vs Bitstamp API", "url": "https://www.anchorterminal.com/compare/binance-vs-bitstamp" }, { "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/coinbase-mcp-vs-dydx.json", "title": "Coinbase MCP server (Coinbase for Agents) vs dYdX", "url": "https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx" } ], "panel": null, "scores": [ { "bitstamp": 63, "by": 8, "coinbase-mcp": 55, "edge": "bitstamp", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "bitstamp": 51, "by": 14, "coinbase-mcp": 65, "edge": "coinbase-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "bitstamp": 58, "by": 8, "coinbase-mcp": 66, "edge": "coinbase-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "bitstamp": 60, "by": 10, "coinbase-mcp": 70, "edge": "coinbase-mcp", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "bitstamp": 20, "by": 20, "coinbase-mcp": 40, "edge": "coinbase-mcp", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "bitstamp": 28, "by": 25, "coinbase-mcp": 53, "edge": "coinbase-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "bitstamp": 53, "by": 9, "coinbase-mcp": 62, "edge": "coinbase-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Coinbase MCP server (Coinbase for Agents) scores 59.6 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 6 of 7 scored categories. Bitstamp API leads on reliability. Both do exchange market data.", "tasks": null, "tutorials": [], "verdicts": { "bitstamp": "Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp", "json": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.min.md" }, "markdown": "Coinbase MCP server (Coinbase for Agents) scores 59.6 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 6 of 7 scored categories. Bitstamp API leads on reliability. Both do exchange market data.\n\n- Bitstamp API: grade D, 50.4/100, rank #948 of 1349. Markdown https://www.anchorterminal.com/tools/bitstamp.md · JSON https://www.anchorterminal.com/api/v1/tools/bitstamp.json\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- 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### Bitstamp API (D)\n\nGood for: An agent that needs a long-running regulated spot venue in the EU, UK and US with a sandbox and per-endpoint key permissions, and can do its own signing.\n\nAhead on:\n- Reliability, 63 against 55\n\nWatch for: No official MCP server, SDK, llms.txt or OpenAPI file; the registry's Bitstamp servers are third parties proxying public market data\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 51\n- Agent ergonomics, 66 against 58\n- Security \u0026 auth, 70 against 60\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 53 against 28\n- Transparency \u0026 trust, 62 against 53\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\n## Why the edge\n\n### Maintenance \u0026 community: Coinbase MCP server (Coinbase for Agents) +25\n\n- Bitstamp API (28): Read as a closed service. The last dated API change is 28 August 2026, 67 days before the check (20). Only one dated entry in the last 90 days, after 1 July and 12 June (0). No public repository or issue tracker, support pages did not load and support.bitstamp.net did not resolve; a changelog exists (8 of 25). No official SDKs and no MCP registry presence of Bitstamp's own (0). No package to assess (0). 20 + 0 + 8 + 0 + 0 = 28.\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\n### Payments \u0026 pricing: Coinbase MCP server (Coinbase for Agents) +20\n\n- Bitstamp API (20): No machine payment protocol (0). The fee schedule page loaded empty, the API's fee endpoints need a key, and no rate could be read, so fees are scored as not published (0, unchecked). The API is free, public endpoints need no key and the sandbox needs no money (20). A person must sign up in a browser with identity checks and mint the key (0). 0 + 0 + 20 + 0 = 20.\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\n### Schema \u0026 documentation: Coinbase MCP server (Coinbase for Agents) +14\n\n- Bitstamp API (51): No OpenAPI or other machine-readable contract was found on the API page or elsewhere (0). No llms.txt or Markdown docs (0). The single documentation page describes each endpoint's purpose and parameters, with notes such as the 10-second cache on open orders and the Travel Rule fields, but not when to use one endpoint over another (14 of 20). Parameters are typed with enumerations (margin mode CROSS or ISOLATED, margin multiplier 1 to 25, order types) and required fields marked (11 of 15). Signing examples in Python, Java and C++, and error families with numbered codes and explanations (13 of 15). Version v2 in the path and header, a dated changelog from 7 April 2023 to 28 August 2026, and a 410.001 code for deprecated endpoints, with no stated notice period (13 of 15). 0 + 0 + 14 + 11 + 13 + 13 = 51.\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\n### Security \u0026 auth: Coinbase MCP server (Coinbase for Agents) +10\n\n- Bitstamp API (60): Revocable HMAC-SHA256 keys with per-endpoint permissions, an IP allow-list, single-use nonces, a timestamp window, sub-account scoping and a one-call kill switch for every key; no key expiry found (24 of 30). Permissions are chosen per endpoint and withdrawals can need Travel Rule address verification, but whether a withdrawal address allow-list exists sits in the unread account settings and no confirmation step is documented for API withdrawals (14 of 20). The API returns exchange data, not third-party text (10). No per-key audit log found; the account's transaction history is the record (4 of 15). security.txt names HackerOne's Robinhood programme but expired on 12 July 2026; no certification page was readable (8 of 20). 24 + 14 + 10 + 4 + 8 = 60.\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\n### Transparency \u0026 trust: Coinbase MCP server (Coinbase for Agents) +9\n\n- Bitstamp API (53): The editorial half. A closed service whose terms of use loaded empty for our reader, so the licence and clauses are unknown (8 of 30). The privacy policy loaded empty, so retention and data handling are unchecked (0 of 30). A 410.001 code marks deprecated endpoints and the changelog records replacements such as `trading-pairs-info` by `markets`, with no notice period stated (8 of 20). Subprocessors and data locations are in the unread privacy policy (0). 8 + 0 + 8 + 0 = 16.\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\n### Reliability: Bitstamp API +8\n\n- Bitstamp API (63): Read with the hosted lines on the HTTP API v2 at www.bitstamp.net/api/v2/. status.bitstamp.net is a Statuspage site with component history (20). Its feed for 5 August to 3 November 2026 has 17 entries, among them withdrawals failing on 14 networks for about 3 hours on 21 August, database maintenance with login failures and intermittent trading interruptions for about 1 hour 44 minutes on 23 September, a 39-minute halt of all markets on 5 August, and delistings and single-asset suspensions. One major (10). Rate limits with numbers, 400 a second and 10,000 per 10 minutes (15). Limit errors are named (400.002, 400.067, 400.068) but there is no Retry-After or backoff guidance, duplicate client order ids are allowed, and the only retry guidance is to check the order after a 500.016 timeout (8 of 15). No SLA found (0). Generally available (10). 20 + 10 + 15 + 8 + 0 + 10 = 63.\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\n## Score by category\n\n| Category | Weight | Bitstamp API | Coinbase MCP server (Coinbase for Agents) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 55 | Bitstamp API +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 51 | 65 | Coinbase MCP server (Coinbase for Agents) +14 |\n| Agent ergonomics | 13% (16.2 this run) | 58 | 66 | Coinbase MCP server (Coinbase for Agents) +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 70 | Coinbase MCP server (Coinbase for Agents) +10 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | Coinbase MCP server (Coinbase for Agents) +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 53 | Coinbase MCP server (Coinbase for Agents) +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 53 | 62 | Coinbase MCP server (Coinbase for Agents) +9 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.4 · D** | **59.6 · C** | |\n\n## Facts side by side\n\n| Fact | Bitstamp API | Coinbase MCP server (Coinbase for Agents) |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Bitstamp Ltd. | Coinbase, Inc. |\n| Hosted endpoint | no (local only) | `https://agents.coinbase.com/mcp` |\n| Transports | | Streamable HTTP, stdio |\n| Auth | API key | OAuth |\n| Pricing | Pay per use | Free |\n| x402 | no | payer tooling only |\n| Licence | Proprietary hosted API under Bitstamp's terms of use, which our reader couldn't load | 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 |\n| Tools exposed | none | 29 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-08-28 | 2026-09-30 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | 2026-05-27 |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | none | 509 npm/wk |\n| Agent reviews | none | 2.5/5 (4) |\n\n## How the scores have moved\n\n### Bitstamp API\n\nNo score change since it was listed.\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## Verdicts\n\n**Bitstamp API.** Bitstamp documents its v2 API on one static page with numeric rate limits, per-endpoint key permissions, an IP allow-list, a kill switch and a sandbox. There is no official MCP server, duplicate client order ids are allowed, and the fee schedule, terms, privacy policy and country list render by script and could not be read.\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## Before you call either\n\n### Bitstamp API\n\n1. Mint a key with only the endpoint permissions the task needs and an IP allow-list; keep `revoke_all_api_keys` in reach as a kill switch\n2. Treat `client_order_id` as a label, not a guard. On a timeout (500.016) fetch the order by client id before resending, because duplicates are accepted\n3. Use a fresh 36-character nonce and a timestamp within 150 seconds of server time on every request, or expect API0004 and API0017\n4. Stay under 400 requests a second and 10,000 per 10 minutes; 400.002 and 400.067 mean back off, and open-orders answers are cached for 10 seconds\n5. Start on sandbox.bitstamp.net with the same paths, and read the fee schedule in a browser before quoting costs, since it is unreadable to a plain fetch\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## Questions\n\n### Which is better for AI agents, Bitstamp API or Coinbase MCP server (Coinbase for Agents)?\n\nCoinbase MCP server (Coinbase for Agents) scores 59.6 (C) on agent readiness against Bitstamp API's 50.4 (D), and leads in 6 of 7 scored categories. Bitstamp API leads on reliability.\n\n### Do Bitstamp API and Coinbase MCP server (Coinbase for Agents) need an API key?\n\nBitstamp API needs an API key. Coinbase MCP server (Coinbase for Agents) uses an OAuth sign-in.\n\n### Can an agent call Bitstamp API and Coinbase MCP server (Coinbase for Agents) without installing anything?\n\nNo hosted endpoint is listed for Bitstamp API. Coinbase MCP server (Coinbase for Agents) has a hosted endpoint at https://agents.coinbase.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"bitstamp\", \"b\": \"coinbase-mcp\"}`. From a terminal: `anchor compare bitstamp coinbase-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bitstamp.json and https://www.anchorterminal.com/api/v1/tools/coinbase-mcp.json\n\n## Other comparisons with Bitstamp API or Coinbase MCP server (Coinbase for Agents)\n\n- [Bitfinex API vs Bitstamp API](https://www.anchorterminal.com/compare/bitfinex-vs-bitstamp.md)\n- [Bitfinex API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitfinex-vs-coinbase-mcp.md)\n- [Bitget vs Bitstamp API](https://www.anchorterminal.com/compare/bitget-vs-bitstamp.md)\n- [Bitget vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bitget-vs-coinbase-mcp.md)\n- [Bithumb Open API vs Bitstamp API](https://www.anchorterminal.com/compare/bithumb-vs-bitstamp.md)\n- [Bithumb Open API vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bithumb-vs-coinbase-mcp.md)\n- [Bitstamp API vs Bybit](https://www.anchorterminal.com/compare/bitstamp-vs-bybit.md)\n- [Bitstamp API vs Coinbase Advanced Trade API](https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-advanced-trade.md)\n- [Bitstamp API vs Crypto.com Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-crypto-com-exchange.md)\n- [Bitstamp API vs Deribit](https://www.anchorterminal.com/compare/bitstamp-vs-deribit.md)\n- [Bitstamp API vs dYdX](https://www.anchorterminal.com/compare/bitstamp-vs-dydx.md)\n- [Bitstamp API vs Gate](https://www.anchorterminal.com/compare/bitstamp-vs-gate-io.md)\n- [Bitstamp API vs Gemini Exchange API](https://www.anchorterminal.com/compare/bitstamp-vs-gemini-exchange.md)\n- [Bitstamp API vs HTX trading API](https://www.anchorterminal.com/compare/bitstamp-vs-htx.md)\n- [Bitstamp API vs Hyperliquid](https://www.anchorterminal.com/compare/bitstamp-vs-hyperliquid.md)\n- [Bitstamp API vs Kraken API](https://www.anchorterminal.com/compare/bitstamp-vs-kraken.md)\n- [Bitstamp API vs KuCoin](https://www.anchorterminal.com/compare/bitstamp-vs-kucoin.md)\n- [Bitstamp API vs MEXC API](https://www.anchorterminal.com/compare/bitstamp-vs-mexc.md)\n- [Bitstamp API vs OKX API](https://www.anchorterminal.com/compare/bitstamp-vs-okx.md)\n- [Bitstamp API vs Uniswap Trading API](https://www.anchorterminal.com/compare/bitstamp-vs-uniswap.md)\n- [Bitstamp API vs Upbit Open API](https://www.anchorterminal.com/compare/bitstamp-vs-upbit.md)\n- [Bybit vs Coinbase MCP server (Coinbase for Agents)](https://www.anchorterminal.com/compare/bybit-vs-coinbase-mcp.md)\n- [Binance API vs Bitstamp API](https://www.anchorterminal.com/compare/binance-vs-bitstamp.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- [Coinbase MCP server (Coinbase for Agents) vs dYdX](https://www.anchorterminal.com/compare/coinbase-mcp-vs-dydx.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": "Bitstamp API vs Coinbase MCP server (Coinbase for Agents)", "url": "" } ], "description": "Coinbase scores 59.6 (C) to Bitstamp's 50.4 (D) for exchange market data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Bitstamp API D 50.4", "Coinbase MCP server (Coinbase for Agents) C 59.6", "scores" ], "h1": "Bitstamp API vs Coinbase MCP server (Coinbase for Agents)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/bitstamp-vs-coinbase-mcp", "published": "2026-10-01", "section": "tools", "title": "Bitstamp vs Coinbase for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/bitstamp-vs-coinbase-mcp" }, "tokens": { "markdown": 6050, "slim": 3430 }, "version": 1 }