directa-mcp
Related Servers
Alternatives to directa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that connects Claude to your eToro account, enabling queries about your portfolio, P\&L, balances, watchlists, live prices, and price history.MIT
- AlicenseBqualityCmaintenanceAn MCP server that enables interaction with the Invertir Online (IOL) trading API through Claude Desktop. It allows users to access their IOL trading account and manage financial operations using natural language.82MIT
- AlicenseAqualityFmaintenanceMCP server for Interactive Brokers API integration, enabling account management, trading, market data, and short selling analysis through Claude.835MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants like Claude with direct access to MetaAPI trading platform. Trade forex, stocks, and commodities through natural language conversations.1-
- FlicenseNot gradedqualityDmaintenanceMCP server exposing Tradier brokerage tools to Claude, enabling account balance checks, position management, order operations, and market data queries.-
- FlicenseNot gradedqualityBmaintenanceA local-first MCP server that connects Claude Code to your Robinhood account, enabling read-only portfolio insights, tax analysis, and natural language queries, with optional human-in-the-loop trading actions.-
TDQS
Scored across 18 tools
Most tools map cleanly to distinct resources and actions, and the descriptions explicitly steer agents toward the right one. A few close pairs—check_connection vs get_darwin_status and get_positions vs get_portfolio_overview—could be confused based on names alone, but the descriptions resolve the boundaries.
All tool names follow a consistent snake_case verb_noun pattern: get_, start_, check_, preview_, place_, modify_, and cancel_. Even the status-style tools read predictably, and there is no mixing of conventions.
At 18 tools, this is slightly above the ideal 3-15 range, but the count is justified by the breadth of the domain: connection lifecycle, account, positions, orders, and market data each have their own focused tools. No tool feels redundant or purely decorative.
The core workflows are well covered: check/start Darwin, read balances and positions, preview/place/modify/cancel orders, and fetch candle/tick data. Minor gaps such as no market-order tool, no execution history, and only today's orders are workable but keep it from being fully complete.