No user-submitted related servers found.
Scored across 168 tools
The 168-tool surface contains multiple clusters of near-overlapping status/health tools (get_bot_health, get_system_health, get_system_status, get_bot_dashboard, get_live_bot_metrics, get_all_bot_metrics) whose boundaries are subtle and require careful reading to distinguish. While many descriptions include 'use for' guidance, the sheer number of similar 'get_*', 'check_*', and 'run_*' tools makes misselection likely for an agent.
Most tools follow a readable snake_case verb_noun pattern (get_live_bot_metrics, run_backtest, create_developer_key), but the set mixes many verb styles and includes noun-style outliers like portfolio_summary, mcp_tool_manifest, graphiti_search, and numerai_status. The naming is not chaotic, but it lacks a single predictable convention across the server.
168 tools is an extreme count, far beyond the 25+ threshold where a tool set becomes very hard to navigate. Even with discover_tools as a meta-helper, the server's surface area is overwhelming and the platform would be better split into focused servers (broker, data, auth, marketplace, monitoring).
The server covers an impressively wide lifecycle: onboarding, auth/MFA, broker OAuth, market data, backtesting, strategy validation, risk guards, bot monitoring, subscription, and marketplace. Minor gaps exist such as no update/delete for registered strategies and some read-heavy areas lacking mutation counterparts, but core workflows have no serious dead ends.