Skip to main content
Glama
BACH-AI-Tools

Indian Stock Exchange API2 MCP Server

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOSTNoHost setting (Not applicable/Optional)
PORTNoPort setting (Not applicable/Optional)
API_KEYYesAPI 密钥 (API Key for Indian Stock Exchange Api2)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
corporate_actionsD

Get Corporate Actions Data

historical_dataC

  • Endpoint: /historical_data - Method: GET - Query Parameters: - stock_name (required): string - period (optional): string, default is \

mutual_fund_searchC

Mutual Fund Search Endpoint: GET /mutual_fund_search Description: This endpoint allows you to search for mutual funds. Parameters: - query (string, required): The search term to query the mutual funds. Response: ```json [ { \

ipoB

Get latest upcoming, listed, active, closed IPO data.

nse_most_activeB

NSE Most Active Endpoint: /NSE_most_active Method: GET Description: Get the latest most active stocks in the National Stock Exchange (NSE) based on trading volume. Example Request: http GET /NSE_most_active Example Response: ```json [ { \

stock_forecastsD

$237

historical_statsC

  • Endpoint: /historical_stats - Method: GET - Query Parameters: - stock_name (required): string - stats (required): string - Description: Retrieve historical statistics for a specific stock. - Example Request: http GET /historical_stats?stock_name=TATAMOTORS\u0026stats=quarter_results

fetch_52_week_high_low_dataD

$238

mutual_fundsC

Mutual Funds Endpoint: /mutual_funds Method: GET Description: Retrieve the latest data for mutual funds, including net asset value (NAV), returns, and other details. Example Request: http GET /mutual_funds Example Response: ```json { \

bse_most_activeB

BSE Most Active Endpoint: /BSE_most_active Method: GET Description: Get the latest most active stocks in the Bombay Stock Exchange (BSE) based on trading volume. Example Request: http GET /BSE_most_active Example Response: ```json [ { \

commodity_futures_data_apiD

$239

get_stock_data_by_nameD

$23a

price_shockersC

Price Shockers Endpoint: /price_shockers Method: GET Description: Get data for stocks that have experienced significant price changes in a short period of time. Example Request: http GET /price_shockers Example Response: ```json [ { \

industry_searchD

$23b

analyst_recommendationsD

$23c

get_trending_stocksD

$23d

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.2/5.0

Scored across 16 tools

Disambiguation3/5

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 Consistency2/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources