mcp-ldbd
Related Servers
Alternatives to mcp-ldbd
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceComprehensive MCP server for real-time stock, cryptocurrency, options, and fundamental analysis, including SEC filings and insider trading data.269 npmMIT
- AlicenseBqualityDmaintenanceAn MCP server that provides comprehensive financial insights and analysis by leveraging real-time market data, news, and advanced analytics for stocks, options, financial statements, and economic indicators.1751PythonMIT
- AlicenseAqualityDmaintenanceA comprehensive MCP server for stock analysis and trading insights, including stock screening, fundamental analysis, insider trading, options analysis, social media research, and news analysis.1075MIT
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables AI assistants to access and analyze financial data, stock information, company fundamentals, market insights, and 250+ tools spanning equities, ETFs, crypto, forex, commodities, and economics.333 npmApache 2.0
- AlicenseAqualityBmaintenanceAn MCP server for the pex.bot AI simulated crypto exchange that enables users to manage accounts, check real-time market data, and execute trades. It provides tools for profile management, order execution, and asset tracking within a simulated cryptocurrency trading environment.1190 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets an AI agent read your portfolio, place paper trades, and check the leaderboard on your ChartObserver account.1313 npmMIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: market data (indicators, asset info, base rates, macro, trending) versus personal actions (submit prediction, my stats, open predictions, track record). Even the 'my' tools are differentiated by open vs resolved vs summary. No two tools could be easily confused.
All tool names follow the strict ldbd_<verb>_<object> pattern in snake_case. Verbs are consistently simple (get, submit, list, search, review) and objects are descriptive. This is a uniformly predictable naming convention.
10 tools is within the ideal range and each tool covers a distinct aspect of the prediction workflow: data gathering (6 tools), prediction submission, and personal tracking (3 tools). The count feels well-scoped with no obvious bloat or redundancy.
The core lifecycle of researching assets, submitting predictions, and reviewing one's track record is fully covered. Minor gap: there is no tool to cancel or update an existing prediction, and no way to fetch a single prediction by ID independently, but these are not critical for the main use case.