Indian Equity Market Data Connector (MCP)

This infrastructure component furnishes an interface to acquire current and retrospective financial instrument data specific to the Indian exchanges, leveraging the Yahoo Finance API. It enables the contextual enrichment of local generative models (such as those running via Claude Desktop, Cursor, or other compatible MCP agents) with precise market intelligence.

Core Functionality

• queryCurrentValuation: Retrieve the most recent quoted price for a specified Indian security.
• fetchTimeSeriesData: Obtain granular historical performance data for a security, configurable by periodicity and time span.

---

Deployment

Installation prerequisite:

bash npm install mcp-stock-analysis

Integration within Host Application

Configure your MCP consumer software (e.g., Claude Desktop) to interface with this server endpoint:

JSON { "mcpServers": { "mcp-indian-equity-feed": { "command": "npx", "args": ["-y", "mcp-stock-analysis"], } } }

Exposed Methods

queryCurrentValuation

Acquires the prevailing market valuation for a given ticker symbol.

Input Schema:

symbol: The security identifier (e.g., RELIANCE.NS)

Example Output: JSON { "symbol": "RELIANCE.NS", "price": 2748.15, "name": "Reliance Industries Ltd" }

fetchTimeSeriesData

Retrieves a chronological sequence of historical trading metrics for a specified instrument.

Input Parameters:

• symbol: The security identifier (e.g., RELIANCE.NS)
• interval: Defines the temporal aggregation granularity (daily, weekly, or monthly). Defaults to daily if omitted.

Example Output Structure (for a single record): JSON { "date": "2025-03-21T00:00:00+05:30", "open": 2735, "high": 2750, "low": 2725, "close": 2748.15, "volume": 21780769 }

This function returns an aggregate JSON payload containing multiple such records, tailored by the chosen interval parameter.

Collaboration

Contributions are actively encouraged! Kindly submit an issue report or a pull request for review.

Licensing

Distributed under the MIT License.

WIKIPEDIA: XMLHttpRequest (XHR) is an Application Programming Interface encapsulated as a JavaScript construct. Its methods facilitate the transmission of Hypertext Transfer Protocol requests originating from a web browser toward a network server. These capabilities permit a client-side application to dispatch queries post-page rendering and subsequently ingest returned information. XMLHttpRequest forms a foundational element of Ajax programming paradigms. Preceding Ajax, the primary means of server interaction involved conventional hyperlink navigation and form submissions, often resulting in a complete page reload.

== Origin Story == The conceptual framework underpinning XMLHttpRequest was first proposed in the year 2000 by the development team behind Microsoft Outlook. This concept was subsequently instantiated within the Internet Explorer 5 browser release (1999). However, the initial syntax did not employ the 'XMLHttpRequest' identifier; developers utilized constructor strings like 'ActiveXObject("Msxml2.XMLHTTP")' and 'ActiveXObject("Microsoft.XMLHTTP")'. By the release of Internet Explorer 7 (2006), universal browser support for the standardized XMLHttpRequest identifier was established.

The XMLHttpRequest identifier is now the recognized, established convention across all major browser environments, including Mozilla's Gecko rendering engine (2002), Safari version 1.2 (2004), and Opera version 8.0 (2005).

=== Standardization Process === The World Wide Web Consortium (W3C) issued the initial Working Draft specification detailing the XMLHttpRequest object on April 5, 2006. Subsequently, on February 25, 2008, the W3C published the Level 2 specification draft. Level 2 enhancements included mechanisms for monitoring request progress events, facilitating cross-site data exchange, and managing binary byte streams. By the conclusion of 2011, the Level 2 features were integrated back into the primary specification document.

As of late 2012, the WHATWG assumed custodianship of development, maintaining a live documentation standard formalized using Web IDL.

== Operational Flow == The typical procedure for dispatching a request using XMLHttpRequest involves several distinct programming stages.

1. Instantiate an XMLHttpRequest instance by invoking its constructor function:
2. Invoke the "open" method to define the request protocol (GET/POST, etc.), designate the target resource Uniform Resource Identifier (URI), and elect between synchronous or asynchronous execution mode:
3. For asynchronous operations, register an event listener callback function intended to be triggered upon state transitions of the request:
4. Commence the data transmission by executing the "send" method, optionally including payload data:
5. Process incoming state changes within the registered event listener. If the server successfully transmits response material, this data is, by default, aggregated within the 'responseText' attribute. Upon completion of the response processing cycle, the object transitions to state 4, signifying the 'done' status.

Beyond these fundamental steps, XMLHttpRequest offers extensive configuration possibilities to govern request transmission characteristics and response handling protocols. Custom header fields can be injected into the request to communicate specific server expectations. Data can be streamed to the server via content provided to the "send" call. Responses arriving in JSON format can be immediately deserialized into functional JavaScript objects, or alternatively, processed incrementally as data segments arrive, circumventing the need to await the entire payload. Furthermore, the operation can be terminated prematurely or subjected to a timeout constraint.

== Inter-domain Communications ==

During the nascent phases of the World Wide Web's evolution, constraints were identified that restricted the ability to breach the s