Skip to main content
Glama
script-dragonmkop8t

cryptopanic-mcp-server

by script-dragonmkop8t
OverviewSchemaRelated ServersScoreDiscussions
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

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions API rate limits (maximum 10 pages) and error conditions (API key not set, request failure), which adds useful context. However, it lacks details on authentication requirements, response format beyond a string, or pagination behavior, leaving gaps for a mutation-free tool.

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?

The description is well-structured with clear sections (Args, Returns, Raises) and uses bullet points for parameter details. It is appropriately sized, but the 'Raises' section could be more concise, and some sentences are slightly verbose (e.g., explaining API limits). Overall, it is efficient with minimal waste.

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?

Given no annotations, 0% schema coverage, and no output schema, the description does a fair job: it covers parameters thoroughly and mentions errors. However, it lacks information on authentication (e.g., how to set the API key), response structure details, or example usage, making it incomplete for optimal agent use.

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?

Schema description coverage is 0%, so the description must fully compensate. It provides detailed semantics for both parameters: 'kind' with valid options ('news' or 'media') and defaults, and 'num_pages' with range constraints (1-10), defaults, and rationale (avoid API rate limits). This adds significant value beyond the bare schema.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Fetch the latest cryptocurrency news from CryptoPanic.' It specifies the action (fetch), resource (cryptocurrency news), and source (CryptoPanic). However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions default values and API constraints but does not specify use cases, prerequisites, or contextual recommendations. Without sibling tools, this is less critical, but the absence of any usage context limits its helpfulness.

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. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedget_crypto_news
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/script-dragonmkop8t/cryptopanic-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server