Indian Stock Exchange API2 MCP Server
Related Servers
Alternatives to Indian Stock Exchange API2 MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables analysis of Indian stocks listed on BSE/NSE through real-time quotes, fundamentals, historical data, stock discovery, market overview, and news integration.13-
- FlicenseAqualityDmaintenanceEnables real-time and historical Indian stock market data retrieval, including prices, news, recommendations, and top gainers/losers.11-
- AlicenseNot gradedqualityDmaintenanceProvides real-time and historical Indian stock market data from NSE and BSE exchanges with 66 tools covering quotes, options chains, corporate actions, IPOs, and market analytics for LLM-powered financial analysis.44 npm12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to perform deep Indian stock research with fundamentals, forensic scores, DCF valuation, screening, and news for 6000+ NSE/BSE stocks.8 npm1MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to real-time Indian stock market data with 34 tools for search, screening, analysis, portfolio tracking, and market insights across all NSE and BSE stocks.118 npm115MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to query live NSE & BSE stock market data, with 55 tools covering quotes, financials, screeners, FII/DII flows, option chains, and company filings.55MIT
TDQS
Scored across 16 tools
Most tools have distinct purposes (e.g., bse_most_active vs. nse_most_active, historical_data vs. historical_stats), but there is some overlap between get_stock_data_by_name and historical_data, and between mutual_funds and mutual_fund_search. The descriptions help clarify differences, but an agent might occasionally misselect between closely related tools.
Naming is inconsistent with mixed conventions: some use snake_case (e.g., analyst_recommendations, get_stock_data_by_name), others use camelCase (e.g., fetch_52_week_high_low_data), and some are abbreviated (e.g., ipo). There's no uniform verb_noun pattern, making the set less predictable and harder to navigate.
With 16 tools, the count is slightly high but reasonable for a stock exchange API covering multiple domains like stocks, commodities, mutual funds, and IPOs. It's borderline heavy but justifiable given the broad scope, though some consolidation might improve coherence.
The toolset covers key areas like stock data, historical info, and market activity, but there are notable gaps: no update or delete operations (expected for an API), and limited coverage for corporate actions or commodity futures beyond basic fetching. It supports core queries but lacks full lifecycle management for the domain.