bykaranteli-mcp
Related Servers
Alternatives to bykaranteli-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceDelivers real-time crypto market microstructure, derivatives, order flow CVD/OI regime classification, fear & greed sentiment, and whale tracking context, enabling traders to assess market regimes and complement charting tools.13 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and trading bots to query live crypto derivatives data across 13 venues, including open interest, funding rates and arbitrage, liquidation cascades, whale positioning with exchange-reported liquidation prices, and tokenized stocks, plus computed regime and risk briefs. It is a read-only remote endpoint requiring no install or API key, and also exposes raw datasets, CSV/Parquet history exports, and webhook alerts for bot workflows.MIT
- AlicenseAqualityBmaintenanceProvides live cryptocurrency market data including spot prices, OHLCV candles, order books, funding rates, and technical indicators via public exchange APIs.8MIT
- AlicenseNot gradedqualityBmaintenanceProvides real-time cryptocurrency market signals including RSI, top gainers, price action, kimchi premium, market prices, and derivatives data from multiple exchanges.MIT
- AlicenseAqualityBmaintenanceAI-native quantitative trading signal engine for crypto and TradFi perpetuals. Multi-factor composite BUY/SELL/HOLD signals, cross-venue funding rate arbitrage scanning, and market regime detection powered by Hyperliquid data.9504 npm10MIT

usenami-mcpofficial
AlicenseAqualityFmaintenancePerp-first funding rate & RWA spread data for AI agents. 30+ CEX/DEX venues, 6 tools (4 x402-paywalled, 2 free), bring-your-own-wallet via Base mainnet.61MIT
TDQS
Scored across 68 tools
Individual descriptions are excellent and frequently disambiguate with explicit pointers ("for a pre-ranked top-10 use get_top_movers instead"), but the set has several crowded families: liquidations appear as get_liquidations, get_liquidation_cascades, get_liquidation_leaderboard, get_liqmap and get_hl_positions; options as get_options_snapshot, get_options_chain, get_options_flow and get_iv_surface; venues as get_venue_markets, get_venue_profile and get_venue_share. get_series additionally overlaps with get_open_interest, get_funding_heatmap, get_rsi_heatmap and most history tools, so an agent must read carefully before selecting.
Every tool uses a snake_case verb_noun pattern with a small, predictable verb set (get_, list_, add_, remove_, create_, delete_, parse_) and resource-oriented nouns that match the domain vocabulary. No camelCase or stylistic mixing anywhere.
68 tools is far beyond what an agent can hold in working context, even though each maps to a real data product on a broad crypto analytics platform. Coverage of exotic niches (tokenized stocks, quantum exposure, Turkey premium, PsiCharge) means many tools are rarely relevant but still consume selection space; splitting into market/derivatives/venues/account subsets would help.
Read coverage across market data, derivatives, venues, macro and on-chain proof is exceptionally thorough with no obvious dead ends for analysis workflows. Gaps are in account management: watchlists can be listed, appended to and pruned but never created, renamed or deleted, and alert recipes can be created/listed/deleted but not updated or toggled enabled/disabled.