A
licenseA
qualityC
maintenanceAn MCP server that tracks newly created liquidity pools on Pancake Swap.
1
10
MIT
crypto-trending-mcp
by kukapay
Provides trending data and market analytics for Bitcoin, including price, percent changes over time, 24h volume, and market cap information.
Delivers trending information and market metrics for Ethereum, showing price movements, trading volume, and market capitalization data.
Offers trending analytics for Solana, including current price, price change percentages, trading volume, and market capitalization metrics.
Click on "Deploy 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., "@crypto-trending-mcpshow me the top 5 trending cryptocurrencies by market cap"
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.
Crypto Trending MCP Server
An MCP server that tracks and monitors the latest trending tokens on CoinGecko, providing real-time insights into the most popular cryptocurrencies.
Features
Tool:
get_trending_md_doc
Returns a Markdown document of the full CoinGecko trending page, including a table of trending cryptocurrencies with columns: Rank, Name, Symbol, Price, 1h Change, 24h Change, 7d Change, 24h Volume, Market Cap.Prompt:
parse_trending_md_doc
Guides MCP clients to extract the trending coins table from the Markdown document and parse it with an LLM, supporting analyses like identifying coins with positive price changes or ranking by market cap.Seamless Integration
Designed for use with Claude Desktop, allowing natural language queries to analyze trending crypto data via MCP tools and prompts.Lightweight & Extensible
Built with minimal dependencies and a simple architecture, making it easy to extend or deploy.
Related MCP server: hf-trending-mcp
Installation
Prerequisites
Python 3.10+
Node.js (for Playwright browser dependencies)
Claude Desktop (optional, for testing with MCP client)
Steps
Clone the Repository:
git clone https://github.com/kukapay/crypto-trending-mcp.git cd crypto-trending-mcpInstall Dependencies with uv:
uv sync playwright install
Usage
Integrating with Claude Desktop
Configure Claude Desktop:
Edit the configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server configuration:
{ "mcpServers": { "crypto-trending": { "command": "uv", "args": [ "--directory", "/absolute/path/to/crypto-trending-mcp", "run", "main.py" ] } } }Replace
/absolute/path/to/crypto-trending-mcpwith the absolute path to yourmain.py.
Restart Claude Desktop:
Close and reopen Claude Desktop.
Look for the hammer icon (🔨) in the input box, indicating MCP tools are available.
Interact with the Server:
Ask natural language questions like:
"What are the trending cryptocurrencies with positive 24h price changes?"
"Show the top 3 trending coins by market cap."
Claude will use the
get_trending_md_doctool andparse_trending_md_docprompt to fetch and analyze the data.
Example Output
The get_trending_md_doc tool returns a Markdown document like:
# Trending Crypto
...
| Rank | Name | Symbol | Price | 1h Change | 24h Change | 7d Change | 24h Volume | Market Cap |
|------|-------------|--------|------------|-----------|------------|-----------|-----------------|-------------------|
| 1 | Bitcoin | BTC | $67,890.12 | +0.45% | +2.34% | +10.12% | $45,123,456,789 | $1,345,678,901,234 |
| 2 | Ethereum | ETH | $2,456.78 | -0.12% | -1.12% | +5.67% | $20,987,654,321 | $295,123,456,789 |
| 3 | Solana | SOL | $167.45 | +0.89% | +5.67% | +15.34% | $3,456,789,123 | $78,901,234,567 |
...
*Data from CoinGecko*The parse_trending_md_doc prompt guides the LLM to extract the table and produce structured output, such as:
[
{
"rank": 1,
"name": "Bitcoin",
"symbol": "BTC",
"price": "$67,890.12",
"change_1h": "+0.45%",
"change_24h": "+2.34%",
"change_7d": "+10.12%",
"volume_24h": "$45,123,456,789",
"market_cap": "$1,345,678,901,234"
},
...
]License
This project is licensed under the MIT License. See the LICENSE file for details.
Available Tools
1 toolget_trending_md_docA
Retrieve a Markdown document containing the CoinGecko trending cryptocurrencies page.
Returns:
A string containing a Markdown-formatted document representing the full CoinGecko trending page.
The document includes:
- Page headers and introductory text.
- A table of trending cryptocurrencies with columns such as Rank, Name, Symbol, Price,
1h Change, 24h Change, 7d Change, 24h Volume, and Market Cap.
- Additional page content like footers, navigation, or metadata.
The trending coins table is embedded within the document and can be extracted for analysis.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves and returns a Markdown-formatted document with specific content, which is useful. However, it lacks details on potential behavioral traits like rate limits, error handling, or data freshness, leaving gaps in transparency.
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 well-structured and front-loaded, starting with the core purpose and then detailing the return content in a bulleted list. Every sentence adds value without redundancy, making it efficient and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is largely complete. It explains the purpose, output format, and content details. However, it could improve by addressing potential limitations or usage context, such as data update frequency or extraction hints, to fully compensate for the lack of structured fields.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description appropriately focuses on the output and content, adding value beyond the schema by detailing what the returned document includes, which is relevant for understanding the tool's semantics.
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 specific action ('Retrieve') and resource ('Markdown document containing the CoinGecko trending cryptocurrencies page'), with no sibling tools to differentiate from. It precisely defines what the tool does without being vague or tautological.
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?
The description implies usage by specifying the content retrieved (trending cryptocurrencies page), but there are no explicit guidelines on when to use this tool versus alternatives, nor any exclusions mentioned. With no sibling tools, this is adequate but lacks proactive guidance.
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
- First observed
get_trending_md_doc
TDQS
A3.9/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
Naming Consistency5/5
A single tool inherently has consistent naming, as there are no other tools to compare against. The name 'get_trending_md_doc' follows a clear verb_noun pattern.
Tool Count2/5
One tool is too few for a server named 'crypto-trending-mcp', which suggests a broader scope for cryptocurrency trending data. A single tool limits functionality and makes the server feel incomplete or trivial for its apparent purpose.
Completeness2/5
The server is severely incomplete for a cryptocurrency trending domain. It only retrieves a Markdown document from CoinGecko, lacking tools for filtering, sorting, analyzing trends, or accessing other trending sources, which are essential for comprehensive coverage.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Crypto market intelligence, token rug-checks, and wallet verification in one MCP server.
Unlock the power of real-time cryptocurrency data with our Crypto Price Insights MCP server.
Official CoinMarketCap MCP server: real-time crypto prices, market cap, rankings and exchange data.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that tracks trending AI models, datasets, and spaces on Hugging Face.4MIT
- AlicenseAqualityFmaintenanceAn MCP server for CoinGecko that connects any MCP-compatible client to free crypto market data, providing tools for prices, market caps, trending coins, historical data, and global stats.829MIT
- AlicenseNot gradedqualityAmaintenanceMCP server providing market data for 15,000+ cryptocurrencies including prices, history, trends, and deep coin metadata via CoinGecko.1011Apache 2.0