Cryptopanic MCP Server

What kukapay/cryptopanic-mcp-server MCP server does

The kukapay/cryptopanic-mcp-server MCP server gives an AI agent access to current cryptocurrency content from CryptoPanic. Its scope is intentionally narrow: it implements one tool for retrieving crypto news or media items. The returned value is a text string containing headline-style results, such as Bitcoin, Ethereum, or regulatory news.

This server fits workflows where an agent needs to check recent crypto coverage before answering a question, summarizing market developments, or monitoring news themes. It does not provide trading operations, price data, portfolio management, or general web search according to the supplied tool description.

How it works

The server calls the CryptoPanic API using credentials supplied in its environment. The tool accepts two parameters:

• kind: selects the content type. Supported values are news and media.
• num_pages: controls how many result pages the server fetches. It defaults to 1 and accepts up to 10 pages.

The available operation is get_crypto_news(kind: str = "news", num_pages: int = 1) -> str. A normal request therefore retrieves one page of news unless the agent specifies another supported content type or page count. The response is returned as text rather than as a documented structured schema.

The kukapay/cryptopanic-mcp-server MCP server is intended to run locally through the project’s Python entry point and communicate with an MCP client over the configured server process. The README shows a uv configuration using the project directory and main.py.

Setup and configuration

Obtain a CryptoPanic API key and API plan through CryptoPanic’s developer portal before starting the server. Configure these values as environment variables:

• CRYPTOPANIC_API_PLAN: the CryptoPanic API plan identifier.
• CRYPTOPANIC_API_KEY: the CryptoPanic API key.

The README’s example starts the project with uv --directory /your/path/to/cryptopanic-mcp-server run main.py. Replace the example directory with the actual local checkout path; the placeholder path is not a runnable value. Add the corresponding server entry to the MCP client’s configuration and provide the two environment variables there.

The project is marked for Node.js 18.x in its repository badges, while the documented launch command uses uv and a Python file. Follow the repository’s current runtime requirements when preparing the local environment. The supplied material does not provide a package-manager installation command or a hosted endpoint.

Tools and capabilities

The kukapay/cryptopanic-mcp-server MCP server exposes one tool:

• get_crypto_news: retrieves CryptoPanic content as text.

Its kind argument distinguishes between news and media. Its num_pages argument can request additional pages, with a maximum of 10. The default call requests one page of news. Example headlines in the README indicate that results can cover individual cryptocurrencies, scaling technologies, exchange-traded-fund developments, and regulation, but the specific content depends on CryptoPanic’s current response.

Limitations and notes

Access depends on a valid CryptoPanic API key and an applicable API plan. The server does not document authentication alternatives, user-specific filtering, symbol filtering, date filtering, sentiment analysis, or article retrieval beyond the single news-fetching tool. The maximum documented request size is 10 pages.

The repository is licensed under MIT. The README mentions another Kukapay news project that does not require an API key, but that is a separate project and is not part of this server’s capabilities.