Cryptocompare

News

news

Read-onlyIdempotent

CoinDesk Data (formerly CryptoCompare) aggregated crypto news feed: Bitcoin/Ethereum/altcoin headlines, exchange announcements, regulatory updates, market analysis. Filter by category (BTC, ETH, Trading, Regulation) or feed. Requires your own CoinDesk Data API key — for crypto news without one, use the crypto-feeds pack instead.

Input Schema

TableJSON Schema

Name	Required	Description
`lTs`	No
`lang`	No
`feeds`	No
`_apiKey`	Yes	Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (get_crypto_price) for prices/daily history or `crypto-feeds` for news instead.
`sortOrder`	No
`categories`	No
`excludeCategories`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`Data`	No	Array of news articles

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "lang": "EN",
-    "sortOrder": "latest"
-  },
-  {
-    "categories": "blockchain",
-    "feeds": "cointelegraph"
-  }
-]New value: +[
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "lang": "EN",
+    "sortOrder": "latest"
+  },
+  {
+    "_apiKey": "your-cryptocompare-api-key",
+    "categories": "blockchain",
+    "feeds": "cointelegraph"
+  }
+]

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Your own CoinDesk Data (formerly CryptoCompare) API key — required, Pipeworx does not supply one for this pack. Free signup: https://developers.coindesk.com/. Without a key, use the `crypto` pack (get_crypto_price) for prices/daily history or `crypto-feeds` for news instead.",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "_apiKey"
+]
```

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "lang": "EN",
+    "sortOrder": "latest"
+  },
+  {
+    "categories": "blockchain",
+    "feeds": "cointelegraph"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "News articles feed",
+  "properties": {
+    "Data": {
+      "description": "Array of news articles",
+      "items": {
+        "properties": {
+          "categories": {
+            "description": "Article categories",
+            "type": "string"
+          },
+          "guid": {
+            "description": "Article GUID",
+            "type": "string"
+          },
+          "id": {
+            "description": "Article ID",
+            "type": "string"
+          },
+          "imageurl": {
+            "description": "Article image URL",
+            "type": "string"
+          },
+          "lang": {
+            "description": "Language code",
+            "type": "string"
+          },
+          "published_on": {
+            "description": "Publication timestamp",
+            "type": "number"
+          },
+          "source": {
+            "description": "News source",
+            "type": "string"
+          },
+          "title": {
+            "description": "Article title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Article URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the read-only/idempotent/non-destructive profile, so the bar is lower. The description adds real behavioral context beyond that: the mandatory own-API-key requirement and the free-signup URL. It doesn't mention pagination or rate limits, but the auth constraint — the most consequential behavioral fact — is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with what the feed contains, then filtering, then the auth requirement. No filler, though the parenthetical 'formerly CryptoCompare' is slightly redundant given it also appears in the API key schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be explained, and the safety profile is covered by annotations. However, for a 7-parameter filtering tool with 14% schema coverage, failing to document the sort order values, category vocabulary, or excludeCategories behavior leaves an agent guessing on core parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, so the description must carry the parameter burden, but it only names `category` and `feed` conceptually. Six of seven params (lTs, lang, feeds, sortOrder, categories, excludeCategories) are undocumented in both schema and description, including enum-like values like sortOrder='latest' and category names that only appear in examples. This is a significant gap for a filtering tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('aggregated crypto news feed'), scopes the content (Bitcoin/Ethereum/altcoin headlines, exchange announcements, regulatory updates, market analysis), and distinguishes itself from siblings by naming `crypto-feeds` and `news_categories`/`news_feeds` territory. An agent can tell what it returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the key usage condition (requires your own CoinDesk Data API key) and names the alternative (`crypto-feeds` pack) for when no key is available. It stops short of stating when-not to use the sibling news tools like `news_categories` or `news_feeds`, but the core routing guidance is explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cryptocompare tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.