A
licenseNot graded
qualityD
maintenanceAn MCP server that provides real-time cryptocurrency news sourced from NewsData for AI agents.
15
MIT
cryptopanic-mcp-server
by kukapay
cryptopanic-mcp-服务器
向 AI 代理提供最新的加密货币新闻，由CryptoPanic提供支持。
工具
服务器只实现一个工具：
get_crypto_news(kind: str = "news", num_pages: int = 1) -> strkind：内容类型（新闻、分析、视频）num_pages：要获取的页面数（默认值：1，最大值：10）
示例输出：
- Bitcoin Breaks $60k Resistance Amid ETF Optimism
- Ethereum Layer 2 Solutions Gain Traction
- New Crypto Regulations Proposed in EU
- ...Related MCP server: ChainGPT MCP
配置
CryptoPanic API 密钥：在此获取
向您的配置文件添加服务器条目：
"mcpServers": {
"cryptopanic-mcp-server": {
"command": "uv",
"args": [
"--directory", "/your/path/to/cryptopanic-mcp-server",
"run",
"main.py"
],
"env": {
"CRYPTOPANIC_API_KEY": ""
}
}
}执照
MIT 许可证 - 请参阅LICENSE文件
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | news | |
| num_pages | No |
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 tool update
v0.1.0- First observed
get_crypto_news
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no ambiguity. The single tool has a clear purpose.
Naming Consistency5/5
With only one tool, naming is self-consistent and follows a verb_noun pattern.
Tool Count2/5
A single tool for a cryptocurrency news server is too few, lacking coverage for related operations like filtering by currency or fetching full articles.
Completeness2/5
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
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Real-time curated crypto news for AI agents with sentiment, recaps, and search.
Free crypto news for agents: top stories by market impact, search, topics, AI digest.
Research articles and live crypto prices for AI agents via x402 on Base.
Crypto market signals, technical indicators, and sentiment analysis for AI agents.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI agents to access crypto-related information including latest news, prices, and market trends through ChainGPT capabilities.329 npm5MIT
- 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