WhyCoinMoves MCP
Related Servers
Alternatives to WhyCoinMoves MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables read-only, remote access to a crypto and AI news archive: fetching the latest articles, searching by keyword, retrieving full machine-readable article text, market ticker snapshots, and a public scoreboard of graded calls. No authentication or local installation is required.MIT
- 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
- AlicenseAqualityBmaintenanceHourly news sentiment and typed market events (hack, regulation, listing, delisting, legal) for 30 crypto pairs, with source links on every signal. Four tools cover the latest score per symbol, history, classified events and the symbol list, and a free API key works out of the box4194 npmMIT
- FlicenseNot gradedqualityBmaintenanceFree, no-auth crypto news API with 200+ sources for fetching real-time and historical crypto news.179 npm330-
- AlicenseNot gradedqualityDmaintenanceReal-time crypto news aggregation with sentiment scores and token mentions, enabling market analysis and trading signals via pay-per-call micropayments.MIT
- AlicenseAqualityDmaintenanceA cryptocurrency news aggregation server providing AI-powered sentiment ratings, trading signals, and real-time market updates. It allows users to search news by coin, source, or engine type and filter results based on AI impact scores and bullish/bearish signals.112,430MIT
TDQS
Scored across 2 tools
get_events and get_coin both surface events, but the boundary is reasonably clear: one is an event feed with optional filters, the other a per-coin snapshot including events. Minor overlap since a coin-scoped get_events call returns much of what get_coin returns.
Both tools follow the same get_<resource> convention, so the pattern is fully predictable.
Two tools is thin for a data product; a coin listing/discovery endpoint would be natural alongside the per-coin lookup, so the surface feels slightly under-scoped rather than fully earned.
Read-only coverage is coherent (event feed + coin snapshot), but there is no way to enumerate supported coins/topics or paginate/history-browse, which are likely dead ends for an agent exploring the dataset.