cryptopanic-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRYPTOPANIC_API_KEY | Yes | Your API key from CryptoPanic | |
| CRYPTOPANIC_API_PLAN | Yes | Your API plan from CryptoPanic (e.g., free, pro) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.