Indian Broker MCP Server
Related Servers
Alternatives to Indian Broker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConsolidates your B3 investment portfolio (stocks, FIIs, fixed income, etc.) from all brokerages into one view. Provides read-only tools to check position, dividends, transactions, and more.MIT
- AlicenseAqualityBmaintenanceRead-only MCP server for INDmoney portfolio and Indian market data, using official REST and WebSocket APIs. Provides tools for account info, quotes, holdings, mutual funds, CAS parsing, and analytics.239 npmMIT
- FlicenseNot gradedqualityDmaintenanceControls and reads a live TradingView Desktop chart via Chrome DevTools Protocol, enabling market scanning, morning briefs, backtesting, and live NSE PCR data through a local dashboard.85 npm-
- AlicenseNot gradedqualityDmaintenanceFetches and normalizes investment portfolio data from eToro and Interactive Brokers (IBKR), enabling AI agents to consolidate, aggregate, and visualize holdings across brokers.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered trading and portfolio management through Upstox API integration. Supports portfolio rebalancing strategies with LLM inference for automated trading decisions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude, LangGraph and other AI agents or CLI clients to read Groww portfolio, quotes and live prices and to place stock and F&O orders through the Groww Trade API. Orders pass through a safety pipeline with dry-run defaults, risk limits, a kill switch and an audit log.MIT
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, but get_positions and get_fno_positions could be confused since F&O positions are a subset of positions. Similarly, get_holdings, get_mutual_funds, get_us_stocks, and get_gold are differentiated by asset type, which is clear. Overall, the tools are separable by their descriptions.
The naming convention is mixed: some tools follow a verb_noun pattern (e.g., get_holdings, search_stock), while others use a noun_verb pattern (e.g., broker_connect, broker_disconnect). This inconsistency is not chaotic but could be more uniform. Both patterns use lowercase with underscores, so it's readable.
14 tools is appropriate for a broker aggregation server. The count is well within the typical 3-15 range, and each tool addresses a specific aspect of broker connectivity, data retrieval, or usability. None feel redundant.
The tool set covers connection management, holdings, positions, and orders, but misses obvious financial data like cash balances and trade history. It also lacks any trading or order placement capabilities, which could be expected for a broker MCP, though it may be intentionally read-only. The core read-only aggregation surface is present, but notable gaps exist.