Tickory MCP Server
OfficialRelated Servers
Alternatives to Tickory MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables scanning and querying stock market data across thousands of US tickers and top cryptos, with tools for signal analysis, historical replay, and webhook subscriptions.3525 npmMIT- FlicenseNot gradedqualityCmaintenancePulls Binance spot candle data, computes technical indicators (RSI, MACD, EMAs), and evaluates user-defined bias and risk rules without needing a TradingView session.47 npm-
- AlicenseNot gradedqualityBmaintenanceEnables scanning Binance USDT pairs for sustained bullish momentum and LONG-only setups, with hybrid intraday/streak safety filtering, individual coin analysis, and active-pair listing through MCP tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously analyze market data, compute risk metrics, and execute spot or futures trades on Binance with safety guardrails like dry-run mode and slippage protection.1-
- AlicenseNot gradedqualityBmaintenanceEnables scanning and analyzing Binance micro/smallcap coins with sustained positive momentum, filtering by volume band and minimum ATR to find asymmetric high-return bets.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to scan crypto and US stocks for beta-adjusted relative strength, momentum signals, RSI readings, and entry/stop/target trade plans, with watchlists validated against live data. Also lets users start a persistent background bot that pushes high-confidence setup alerts via desktop notifications or Discord/Slack webhooks.1MIT
TDQS
Scored across 18 tools
All 18 tools have clearly distinct purposes. List vs. get, run vs. ad-hoc, and relay lifecycle tools (sources, events, traces, replay) are all well-separated, minimizing agent confusion.
All tools follow a consistent 'tickory_verb_noun' pattern (e.g., tickory_create_scan, tickory_list_alert_events). No mixing of styles or vague verbs.
18 tools is above the typical 3-15 range but still justified for the breadth of functionality (relays, scans, alerts, market data). Each tool has a distinct role, so it feels well-scoped rather than bloated.
Core workflows for scans, relays, and alerts are present (create, read, list, update, run). However, no delete or deactivate operations exist for scans, relay sources, or alerts, which are notable gaps for a complete lifecycle.