CoinDesk
by CoinDesk
Query live and historical crypto spot, futures, options, index and news data from an AI agent. CoinDesk's own page lists 39 read-only tools; Anthropic's directory lists 24. OAuth sign-in wrapping your CoinDesk API key, and a licence that restricts what you may do with the answers.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect CoinDesk via MCP
https://mcp.coindesk.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
CoinDesk Tools & Capabilities (39)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The licence is the binding constraint, not the tool surface. Internal use only, no Display without written permission, no Index or Financial Product. Most of what people want an agent for — answering a colleague, powering a dashboard, feeding a signal — is addressed by one of those three clauses. Read the agreement before deploying, and get written permission where the use goes beyond your own desk.
- The agreement says nothing about AI, RAG or model training. Verified across the full text on 2026-08-22. That is a gap in the drafting rather than a grant, and it leaves agent use to be judged under clauses written for conventional applications.
- No OAuth scope boundary exists.
scopes_supportedis declared as an empty array and the RFC 9728 descriptor omits the field. Nothing at consent distinguishes one dataset from another. The read-only property comes from the API being GET-only. - Anthropic's directory under-lists by 15 tools and names 3 that CoinDesk does not. Any client built against the directory's
fetch_spot_orderbook,fetch_futures_orderbookorfetch_options_orderbookis calling names the vendor no longer publishes. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous
initializeon 2026-08-22, so noreadOnlyHint,destructiveHintor parameter detail is published here. The read-only classification rests on the vendor's names and the GET-only specification, not on the server's own declaration. - Some data needs a paid plan. The specification annotates endpoints with
x-roles-required; 33 paths requirepremiumalongsidefree, and five require aforex_rates_viewerrole. A tool that works on one account may return an authorisation error on another, and the tool list gives no hint which. - No tool reports rate-limit status. The accounting endpoint exists in the API and is not exposed through MCP. Plan long historical pulls deliberately.
- Thirty-five of the 184 API paths are tagged Deprecated, including several
/v1/marketsendpoints superseded by/v2/. Which MCP tool maps to which version is not published, so a tool may sit on a deprecated path without saying so. - The data is not intended for trading. CoinDesk's clause 10.1.1 states this outright and has you acknowledge that interpreting the data requires specialist market knowledge. Responses are cached — the specification declares cache windows from 0 to 3,600 seconds per endpoint — so a "current" price may be up to an hour old depending on which endpoint answered.
developers.coindesk.comserves one SPA shell for every path./llms.txt,/faq/and/documentationall returned a byte-identical 7,844-byte Nuxt shell on 2026-08-22. The Special Terms the licence points to at/faq/could not be read, so no claim is made about what they add. The machine-readable specification was recovered from the URL the site's own JavaScript bundle fetches.
Frequently asked questions
No. Every one of the 39 tools CoinDesk lists begins with fetch, and the OpenAPI specification behind them defines 184 paths of which all 184 are GET. There is no POST, PUT, PATCH or DELETE anywhere in the surface. The connector reads market data and news, and nothing in it can write to an exchange or an account.
CoinDesk's own page lists 39, and Anthropic's directory lists 24. The eighteen names the directory omits include the entire on-chain DEX group and both split orderbook tools. Three directory names, such as fetch_spot_orderbook, appear on no CoinDesk page at all. Trust CoinDesk's list and expect the directory to lag.
Not without written permission. CoinDesk's API Licence Agreement grants an internal-use-only licence and clause 2.4.1 forbids using licenced data for Display purposes, which the Schedule defines as making it available for viewing on a website or through an application. An agent surfacing a price to anyone but you is likely a Display use.
No call is billed individually, but every call consumes your account's rate-limit allowance. CoinDesk enforces limits at account level across all API keys, at second, minute, hour, day and month granularity, and returns HTTP 429 on breach. No MCP tool reports remaining allowance, so an agent cannot check before spending it.
A CoinDesk Data API key. CoinDesk's MCP page states the server uses OAuth 2.0 with PKCE and that on first connection you are prompted to enter your API key, which is then encrypted and used to authenticate requests on your behalf. Existing customers find the key in developer settings; others must register interest first.
Treat it as untrusted input. The news endpoints return a BODY field carrying article text sourced from third-party outlets rather than CoinDesk alone. Any publisher whose feed CoinDesk ingests can therefore place text into your agent's context, which makes fetch_news a prompt-injection surface. Read retrieved articles as data, never as instructions.
No. Clause 2.4.3 of CoinDesk's API Licence Agreement forbids using licenced data to create or in connection with any Index or Financial Product, and clause 10.1.1 has you acknowledge the data is not intended for trading purposes. Both definitions in the Schedule are drawn broadly.
None. The server's authorization server metadata declared scopes_supported as an empty array on 2026-08-22, and its RFC 9728 resource descriptor omits the field entirely. There is no scope boundary at consent. The read-only boundary here comes from the API being GET-only, not from anything the OAuth grant enforces.
Sources
- CoinDesk Data MCP server page (retrieved 2026-08-22). Source of the 39-tool list, the OAuth-with-PKCE description, the API-key prompt and the example prompts. · retrieved 2026-08-22
- CoinDesk API OpenAPI 3.0.3 specification, version 2.1.1976 (retrieved 2026-08-22). 184 paths, all GET; source of the rate-limit, role-gating, caching, news-schema and deprecation facts. Located via the URL referenced in the documentation site's own JavaScript bundle. · retrieved 2026-08-22
- CoinDesk API Licence Agreement, dated 22 April 2026 (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check — anonymous
initializetohttps://mcp.coindesk.com/mcpreturned 401 with awww-authenticatechallenge; RFC 9728 metadata athttps://mcp.coindesk.com/.well-known/oauth-protected-resourceand authorization server metadata athttps://mcp.coindesk.com/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- CoinDesk support — <mailto:support@coindesk.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- CoinDesk
- Tools
- 39
- Domain
- mcp.coindesk.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.