cryptopanic-mcp-server
The cryptopanic-mcp-server provides access to the latest cryptocurrency news via the CryptoPanic API.
With this server, you can:
Fetch cryptocurrency news with the
get_crypto_newstoolSpecify content type (
news,analysis, orvideos) using thekindparameterControl the number of pages to fetch (up to 10) with the
num_pagesparameterIntegrate with AI agents to deliver real-time crypto updates
The server requires configuration with a CryptoPanic API key for access.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cryptopanic-mcp-serverget the latest crypto news"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cryptopanic-mcp-server
Provide the latest cryptocurrency news to AI agents, powered by CryptoPanic.
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) -> strkind: 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 MCP
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-serverwith your actual installation path.Replace
CRYPTOPANIC_API_PLANandCRYPTOPANIC_API_KEYwith your API plan and key from CryptoPanic.
License
MIT License - see LICENSE file
Available Tools
1 toolget_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.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | news | |
| num_pages | No |
TDQS
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.
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.
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.
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.
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.
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.
TDQS
Only one tool exists, so there is no ambiguity. The single tool has a clear purpose.
With only one tool, naming is self-consistent and follows a verb_noun pattern.
A single tool for a cryptocurrency news server is too few, lacking coverage for related operations like filtering by currency or fetching full articles.
The tool only fetches news titles as a concatenated string, missing functionalities like detailed article retrieval, search, or category-based filtering, making it severely incomplete.
Maintenance
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
Real-time curated crypto news for AI agents with sentiment, recaps, and search.
Crypto market signals, technical indicators, and sentiment analysis for AI agents.
Real-time financial news for AI agents: search by ticker and source, with sentiment and entities.
AI-enriched financial news for AI agents & trading bots: search, trending, insider, scored 1-10.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides real-time cryptocurrency news sourced from NewsData for AI agents.15MIT
- AlicenseAqualityCmaintenanceEnables AI agents to access crypto-related information including latest news, prices, and market trends through ChainGPT capabilities.3375MIT
- AlicenseAqualityDmaintenanceProvides AI agents with real-time cryptocurrency news and media updates sourced from CryptoPanic. It allows users to fetch multiple pages of content to track market sentiment and the latest developments in the crypto space.1MIT
- AlicenseBqualityFmaintenanceReal-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.4MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/kukapay/cryptopanic-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server