Stochastly MCP
Related Servers
Alternatives to Stochastly MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes market data, public strategies, backtesting, subscriptions, and AI generation capabilities as MCP tools that AI clients such as Claude Desktop, Cursor, and Cline can call. It runs locally over stdio or remotely over Streamable HTTP, with anonymous, API-key, or OAuth access.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceBridges a local Tongdaxin client to MCP, exposing tools for market data, financial information, sector management, terminal push, simulated trading, and automatic price alerts, enabling natural-language data retrieval, analysis, and order operations through agents.5MIT
- FlicenseNot gradedqualityDmaintenanceExposes TradingView technical indicators and OHLCV data through MCP tools for Claude Desktop or any MCP-aware client.26-
- FlicenseNot gradedqualityCmaintenanceLets Claude Code drive the local MindStrat desktop trading app through its own screen endpoints, covering market data downloads, MSF strategy authoring, backtests, optimizer and robustness runs, and portfolio/live deployment with gated confirmations. It also serves the app's manual as resources so the agent can write strategies that behave identically in live and backtest.-
- AlicenseAqualityBmaintenanceStdio proxy for HirePulse: 27 live tools for company research, hiring, job changes, public contacts and commerce evidence. Focused remote profiles: 9 B2B or 11 commerce tools. Free sandbox, 10 successful calls per agent per UTC day (shared network ceiling), and eligible 25-call trials. Paid results use x402 USDC on Base. Install: npx -y hirepulse-mcp (Node.js 20+).2649 npm1MIT
- AlicenseNot gradedqualityAmaintenanceConnects AI clients such as Claude Code, Cursor, Codex, ChatGPT, Hermes, and OpenClaw to 2,000+ AI models and data APIs through a local MCP bridge, letting an agent discover, inspect, price, and run tools after a single browser-approved OAuth sign-in. Backed by a read-only catalog, run history, and rollback so calls can be audited and reverted without managing individual API keys.556,724 npmMIT
TDQS
Scored across 29 tools
Most tools target a distinct resource+action (compose_graph vs backtest_graph vs backtest_status, export_paper vs export_atlas vs export_tearsheet, the v9_* scanner family vs the backtest_* graph family). A few clusters overlap thematically, notably the evaluation tools (red_flag_check, adversarial_check, reality_check_profiles, diagnostics_catalog/explain) and the app-control trio (live_state, set_live_state, pilot_app), but descriptions explicitly cross-reference 'use X instead', resolving most confusion.
Everything is snake_case with a predictable, readable style and useful subsystem prefixes (backtest_, export_, diagnostic_, v9_). The main deviation is that some tools are verb_noun (compose_graph, export_paper, red_flag_check) while others are noun-only (app_info, data_sources, node_catalog, live_state), so the verb pattern isn't fully uniform.
29 tools is on the heavy side and includes clear bloat (set_live_state is explicitly legacy, run_smoke_tests is dev-only), which everyone pays the surface-area cost for. Still, the server spans genuinely different subsystems—graph backtesting, a separate batch scanner, portfolio combination, report export, diagnostics, and app piloting—so the count is defensible rather than gratuitous.
The research lifecycle is well covered: discover nodes/registries/data sources, compose and run graphs, poll status, judge results (red_flag_check, adversarial_check, portfolio_combine), and export papers/tearsheets, plus the parallel v9 scanner surface and app/diagnostics introspection. Minor gaps exist—e.g. no tool to enumerate the day's session run registry directly, and inspection of graph runs depends on a run_id from a prior call—but these are workable.