Skip to main content
Glama
script-dragonmkop8t

cryptopanic-mcp-server

by script-dragonmkop8t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cryptopanic-mcp-server

Provide the latest cryptocurrency news to AI agents, powered by CryptoPanic.

License Node.js Status

Try Kukapay News MCP — no API key required, fully AI-annotated.

Tools

The server implements only one tool: 

get_crypto_news(kind: str = "news", num_pages: int = 1) -> str

  • kind: Content type (news, media)

  • num_pages: Number of pages to fetch (default: 1, max: 10)

Example Output: 

- Bitcoin Breaks $60k Resistance Amid ETF Optimism
- Ethereum Layer 2 Solutions Gain Traction
- New Crypto Regulations Proposed in EU
- ...

Related MCP server: ChainGPT AI News MCP Server

Configuration

  • CryptoPanic API key & API plan: get one here

  • Add a server entry to your configuration file:

"mcpServers": { 
  "cryptopanic-mcp-server": { 
    "command": "uv", 
    "args": [ 
      "--directory", 
      "/your/path/to/cryptopanic-mcp-server", 
      "run", 
      "main.py" 
    ], 
    "env": { 
      "CRYPTOPANIC_API_PLAN": "your_api_plan",
      "CRYPTOPANIC_API_KEY": "your_api_key" 
    } 
  } 
}

  • Replace /your/path/to/cryptopanic-mcp-server with your actual installation path.

  • Replace CRYPTOPANIC_API_PLAN and CRYPTOPANIC_API_KEY with your API plan and key from CryptoPanic.

License

MIT License - see LICENSE file

Available Tools

1 tool
get_crypto_newsA

Fetch the latest cryptocurrency news from CryptoPanic.

Args: kind (str, optional): Type of content to fetch. Valid options are: - 'news': Fetch news articles (default). - 'media': Fetch media content like videos. num_pages (int, optional): Number of pages to fetch (each page contains multiple news items). Defaults to 1. Maximum is 10 to avoid API rate limits.

Returns: str: A concatenated string of news titles, each prefixed with a dash (-).

Raises: ValueError: If the API key is not set or if the API request fails.

ParametersJSON Schema
NameRequiredDescriptionDefault
kindNonews
num_pagesNo

TDQS

A4.4/5.0
Behavior4/5

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

Without annotations, the description explains return format, exception handling (ValueError for missing API key or failed request), and rate limits (max 10 pages). This provides solid transparency, though some behavioral details like idempotency are not mentioned.

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

Conciseness5/5

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

The description is concise and well-structured, with a clear first sentence stating the purpose, followed by parameter details, return type, and exceptions. Every sentence serves a purpose.

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

Completeness5/5

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

For a simple tool with two optional parameters and no output schema, the description covers all necessary aspects: purpose, parameters, return value, and error handling. No gaps are evident.

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

Parameters5/5

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

Despite 0% schema coverage, the description fully explains both parameters: 'kind' with valid options (news/media) and 'num_pages' with default and maximum. This adds significant value beyond the schema's minimal information.

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 clearly states the tool fetches cryptocurrency news from CryptoPanic. It specifies the verb 'fetch', the resource 'cryptocurrency news', and the source, leaving no ambiguity.

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

Usage Guidelines3/5

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

No guidance on when to use this tool versus alternatives is provided. Since no sibling tools exist, the inference is that it is the only news-fetching tool, but explicit context is missing.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedget_crypto_news
Deploy Server
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

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching cryptocurrency news from CryptoPanic, with no other tools to confuse it with.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_crypto_news' follows a clear verb_noun pattern, and there are no other tools to deviate from this pattern.

Tool Count2/5

A single tool is too few for a server focused on cryptocurrency news, as it lacks essential operations like filtering by category, searching, or retrieving specific news items. This minimal scope will likely cause agent failures due to incomplete functionality.

Completeness2/5

The tool surface is severely incomplete for a cryptocurrency news domain. It only allows fetching general news with basic pagination, missing critical features such as filtering by coin, date, or sentiment, as well as operations like detailed article retrieval or subscription management.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • market-data-mcp

    aviman1109
    A
    license
    Not graded
    quality
    D
    maintenance
    Integrates cryptocurrency market data from CoinGecko, the Fear & Greed Index, and CryptoPanic news into a single toolset for AI agents. It enables users to retrieve global market statistics, trending assets, coin-specific details, and real-time news feeds.
    MIT

  • cryptopolitan-mcp

    4dmrkey
    A
    license
    B
    quality
    F
    maintenance
    Real-time cryptocurrency news, analysis, and price predictions for AI agents. 5 tools to search 50,000+ articles across 12 categories, filter by 120+ asset tickers, and access content with built-in attribution. Free with attribution. SSE and Streamable HTTP transport.
    4
    MIT