crypto-feargreed-mcp
Related Servers
Alternatives to crypto-feargreed-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server providing market data for 15,000+ cryptocurrencies including prices, history, trends, and deep coin metadata via CoinGecko.43 npm1Apache 2.0
- AlicenseAqualityFmaintenanceAn MCP server that delivers cryptocurrency sentiment analysis to AI agents.547MIT
- FlicenseAqualityBmaintenanceMCP server providing 10 crypto/DeFi data tools (prices, gas, Fear & Greed, TVL, etc.) with no API keys required.101-
- AlicenseNot gradedqualityFmaintenanceAn MCP server that provides real-time funding rate data across major crypto exchanges.8MIT
- AlicenseAqualityDmaintenanceAn MCP server that aggregates real-time cryptocurrency news from multiple RSS feeds.217MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents the ability to check crypto wallet balances, track token prices, calculate portfolio value, monitor gas prices, and track the Fear & Greed Index — all with zero external dependencies using free public APIs.MIT
TDQS
Scored across 3 tools
The tools have overlapping purposes that could cause confusion. 'analyze_fng_trend' and 'get_historical_fng_tool' both retrieve historical data with a 'days' parameter, making their boundaries unclear. 'get_current_fng_tool' is distinct but the other two appear to serve similar functions with minor differences in output format.
The naming follows a mixed convention. 'analyze_fng_trend' uses snake_case with a verb_noun pattern, while 'get_current_fng_tool' and 'get_historical_fng_tool' also use snake_case but append '_tool' inconsistently. The pattern is readable but lacks full consistency across all tools.
With 3 tools, the count is reasonable for a focused server on Crypto Fear & Greed Index data. It's slightly thin but covers current, historical, and trend analysis, which aligns well with the domain scope without being overly complex.
The tool surface covers basic retrieval and analysis of the index, but there are notable gaps. For example, there's no tool for comparing multiple time periods, setting alerts, or integrating with other crypto data, which could limit agent workflows in a broader crypto analysis context.