Back to MCP directory
publicPublicdnsLocal runtime

cryptopanic-mcp-server

向人工智能代理提供最新的加密货币新闻。

article

README

cryptopanic-mcp-server

Discord GitHub License

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

cryptopanic-mcp-server MCP server

Tools

The server implements only one tool:

get_crypto_news(kind: str = "news", num_pages: int = 1) -> str
  • kind: Content type (news, analysis, videos)
  • 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
- ...

Configuration

  • CryptoPanic API key: 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_KEY": "" 
    } 
  } 
}

License

MIT License - see LICENSE file

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client