Avanza-MCP
Related Servers
Alternatives to Avanza-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLocal Streamable HTTP MCP server for Avanza that provides authentication, account data, instruments, market data, and order tools. Order tools can affect real money, so requires approval and safe configuration.MIT
- FlicenseAqualityDmaintenanceMCP server for the tastytrade brokerage API, providing tools for account management, market data, and order execution.18-
- AlicenseNot gradedqualityDmaintenanceMCP server for Tradernet/Freedom24 trading platform API, enabling portfolio management, order placement, quotes, ticker search, and price alerts via AI assistants.49MIT
- AlicenseBqualityDmaintenanceMCP server for Angel One SmartAPI. Lets AI clients trade Indian stocks, manage orders and GTT rules, read holdings/positions/funds, fetch quotes/candles/OI/Greeks, and estimate margin/brokerage with TOTP login and built-in safety guards.3233MIT
- AlicenseCqualityAmaintenanceLocal paper-trading and market simulation MCP server for multi-account portfolios, advanced orders, options/futures, backtesting, alerts, and automation.60MIT
- AlicenseAqualityBmaintenanceMCP server for the Trading 212 public API, enabling account, portfolio, order, pie, and history access with read tools always available and trading tools opt-in.131MIT
TDQS
Scored across 82 tools
Many tools overlap in scope: avanza_status, avanza_capabilities, and data_source_status all report state, while multiple order and audit tools have near-identical names such as avanza_open_orders vs avanza_ongoing_orders and avanza_open_order_cancel vs avanza_order_delete. The descriptions help, but an agent would frequently struggle to pick the correct tool.
The server broadly uses avanza_* and tv_* prefixes with readable verb_noun names, but consistency breaks down with aliases like avanza_open_order_cancel vs avanza_order_delete, adjective-noun names like avanza_live_snapshot, and mixed provider prefixes like zacks_scrape_symbol vs fmp_analyst_recommendations.
82 tools is far beyond the typical well-scoped MCP server and includes many aliases, per-instrument read variants, and overlapping audit helpers. Even with multiple integrations, the tool surface feels inflated rather than carefully pruned.
Core workflows are well covered: live and paper order lifecycle, stop-loss management, portfolio/position reads, quotes, transactions, account selection, multi-source market data, and strategy audits. Minor gaps exist, such as no dedicated single-order status fetch or paper stop-loss edit tool, but the main strategy-protection workflow has no obvious dead ends.