Skip to main content
Glama

Related Servers

Alternatives to etrink-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Cloud-hosted MCP server that connects AI clients to MetaTrader 4/5 for live prices, account state, indicators, and trades with dry-run safety via natural language.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Universal MCP server that enables AI assistants to control MetaTrader 5 directly, executing trades, managing data, and automating MT5 operations through natural language.
      4
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for MetaTrader 5 that provides account monitoring, risk checks, and Algo Trading toggle without trading operations. Designed to work over SSH across Windows sessions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for E*TRADE that reads account balances, positions, transactions, and orders, with optional opt-in order placement via a two-step preview-confirm handshake.
      35 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for operating headless MetaTrader 5 terminals — over SSH, from your agent.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables trading on MetaTrader5 platform via MCP, including account management, order placement, market data, technical indicators, and signal tools.
      6
      -

    TDQS

    B3.4/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action: service lifecycle (create/deploy/start/stop/restart/rollback/delete), observability (get_service, get_build, get_service_logs, list_releases), and MT5 trading (accounts, positions, orders, signals, reports, trades). The one real collision is get_positions (single account, live) versus get_open_positions (all accounts, last snapshot), which return near-identical data and invite misselection; get_recent_signals vs get_trades vs get_report are close but descriptions differentiate them (events vs closed trades vs aggregate).

    Naming Consistency4/5

    All 23 names are snake_case with a leading verb (list_/get_/create_/delete_/update_/start_/stop_/restart_/deploy_/rollback_/set_/exec_in_), which is highly predictable. Minor deviations: get_build and list_releases omit the '_service'/'service_' qualifier that the other ~15 hosting tools use, making them look domain-agnostic even though they are service-scoped.

    Tool Count3/5

    23 tools is heavy for a single server, and the surface is really two products stapled together (~15 hosting tools plus ~8 MT5 trading tools). Each half is reasonably scoped on its own, but the combined set exceeds the comfortable 3-15 range and increases selection cost.

    Completeness4/5

    Hosting coverage is essentially complete: create, deploy, build status, releases, logs, env, start/stop/restart, rollback, update, delete, plus one-off exec — no dead ends. Trading coverage handles accounts, positions, order placement/close, signals, trades and reporting, but lacks account-level operations (update/delete account, balance/deposit history) and richer order management (modify SL/TP, pending orders).

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data