diyan-research-mcp
Related Servers
Alternatives to diyan-research-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceRead-only MCP server for short-term stock and ETF market research, providing tools for futures, premarket movers, market breadth, earnings, watchlist signals, and daily briefings.-
- FlicenseNot gradedqualityBmaintenanceA research-only MCP server providing read-only data, analytics, and intelligence for Polymarket BTC 5-minute Up/Down markets, enabling LLM agents to query market snapshots, performance metrics, and strategy candidates.-
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server for operator-grade release inspection and benchmark browsing.2 npm1MIT
- AlicenseNot gradedqualityAmaintenanceProvides read-only MCP tools for market snapshots, position risk, order reconciliation, and daily report previews with deterministic financial calculations, evidence chains, and audit trails.MIT
- AlicenseAqualityBmaintenanceA read-only MCP server for EdgeDepth's market microstructure search engine, enabling users to query recorded crypto and TradFi perpetuals for market conditions, outcomes, and reproducibility-keyed evidence directly from MCP clients.101,033 npm3MIT
- FlicenseNot gradedqualityBmaintenanceRead-only MCP server for Taiwan active ETF research database, providing tools to list ETFs, track buy/sell deltas, view stock history and PnL, and find consensus buys across ETFs.5-
TDQS
Scored across 6 tools
Each tool targets a distinct research artifact—framework, stock snapshot, hypothesis, radar, IC backtest, and safe analysis—with no overlap in purpose. The descriptions clearly delineate what each returns, eliminating ambiguity.
Tool names mix noun compounds (framework_excerpt, ic_backtest_summary) with verb-suffix patterns (hypothesis_get, cognition_radar_read) and a verb-adjective combo (research_analyze_safe), lacking a unified convention. This inconsistency makes the naming pattern hard to predict.
Six tools is well within the ideal 3-15 range and appropriately scoped for a read-only research server providing diverse artifact views. Each tool earns its place without bloat.
The surface covers multiple research components, but lacks discovery tools to list available frameworks, stocks, or hypotheses. This could require agents to have prior knowledge of entity identifiers, creating a notable gap in usability.