bharatstock-mcp 0.1.0 → 0.1.2

package/CHANGELOG.md

@@ -2,6 +2,23 @@
 
 All notable changes to `bharatstock-mcp` are documented here (newest first).
 
+## 0.1.2 (2026-10-05)
+
+- Bumped the `bharatstock` JS SDK dependency to ^0.1.11, which made paginated
+  responses forward-compatible: every top-level envelope field and every row
+  field the API returns now passes through unchanged. As a result the MCP
+  tools surface any new/modified API field (e.g. a scheme portfolio's
+  `coveragePct`) with no tool or schema change here.
+
+## 0.1.1 (2026-09-20)
+
+- Added two mutual-fund portfolio tools: `list_mutual_fund_portfolios`
+  (discover the schemes we hold monthly portfolio data for, keyed by the
+  holdings scheme-name) and `get_mutual_fund_portfolio_holdings` (a scheme's
+  equity portfolio for a month, with month-over-month quantity change). These
+  are the inverse of `get_mutual_fund_holdings` and are keyed by the holdings
+  scheme-name string, not the AMFI scheme_code.
+
 ## 0.1.0 (2026-09-22)
 
 - Initial release.

package/README.md

@@ -72,6 +72,8 @@ Each tool wraps a consumer-facing BharatStock endpoint. Your model picks the rig
 - `get_mutual_fund_nav` — daily NAV history
 - `get_mutual_fund_returns` — trailing returns (1m…5y, CAGR)
 - `get_mutual_fund_holdings` — which funds hold a given stock
+- `list_mutual_fund_portfolios` — discover schemes we have portfolios for (by scheme name)
+- `get_mutual_fund_portfolio_holdings` — a scheme's equity portfolio for a month (inverse of holdings)
 
 **Platform**
 - `get_data_status` — public data-integrity/freshness report
@@ -126,4 +128,6 @@ MIT
 
 ## Changelog
 
+- **0.1.2** (2026-10-05): picks up `bharatstock` JS SDK 0.1.11, whose paginated responses now pass through every API field (new or modified) with no SDK change — so every field the API returns (e.g. a scheme portfolio's `coveragePct`, and anything added later) now flows through to the MCP tool output. No tool/schema change.
+- **0.1.1** (2026-09-20): added two mutual-fund portfolio tools — `list_mutual_fund_portfolios` (discover the schemes we hold monthly portfolio data for, by scheme name) and `get_mutual_fund_portfolio_holdings` (a scheme's equity portfolio for a month, with month-over-month quantity change). These are the inverse of `get_mutual_fund_holdings` and are keyed by the holdings scheme-name string, not the AMFI scheme_code.
 - **0.1.0** (2026-09-22): initial release. Local stdio server (`bharatstock-mcp`) + remote Streamable HTTP server (`bharatstock-mcp-http`, multi-tenant, Bearer/X-API-Key auth). MCP is a Developer/Pro feature, gated via `/v1/mcp/authorize`. Tools for stocks (quote, profile, prices, financials, fundamentals, technicals, shareholding, corporate actions, deals, insider trades, peer compare), discovery (search, movers, price shockers, screener), indices, market-wide (FII/DII, deals, insider), and mutual funds (schemes, scheme, NAV, returns, holdings), plus data status.

package/dist/{chunk-RPAWW7CN.js → chunk-LW5UFTIW.js}

@@ -43,7 +43,7 @@ import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { BharatStock } from "bharatstock";
 import { z } from "zod";
 var SERVER_NAME = "bharatstock";
-var SERVER_VERSION = "0.1.0";
+var SERVER_VERSION = "0.1.2";
 async function run(fn) {
   try {
     const data = await fn();
@@ -436,6 +436,34 @@ function buildServer(options = {}) {
     },
     async ({ ticker: ticker2, month, page, pageSize }) => run(() => client.stocks.mfHoldings(ticker2, { month, page, pageSize }))
   );
+  server.registerTool(
+    "list_mutual_fund_portfolios",
+    {
+      title: "List / search mutual-fund portfolios",
+      description: "List/search the mutual-fund schemes we hold monthly PORTFOLIO data for (scheme discovery, to populate a picker). This is the INVERSE of get_mutual_fund_holdings: that answers 'which funds own stock X', this answers 'which schemes do we have portfolios for'. Each row is keyed by the holdings scheme-NAME string (NOT the AMFI scheme_code used by the scheme/NAV tools) and has no Direct/Regular distinction, since AMFI publishes monthly portfolios at the scheme level. Use the returned scheme_name with get_mutual_fund_portfolio_holdings.",
+      inputSchema: {
+        q: z.string().optional().describe("Substring match on scheme name."),
+        fundHouse: z.string().optional().describe("Filter by fund house (substring)."),
+        limit: z.number().int().positive().max(200).optional(),
+        offset: z.number().int().nonnegative().optional()
+      }
+    },
+    async ({ q, fundHouse, limit, offset }) => run(() => client.mutualFunds.listPortfolios({ q, fundHouse, limit, offset }))
+  );
+  server.registerTool(
+    "get_mutual_fund_portfolio_holdings",
+    {
+      title: "Get a mutual-fund scheme's portfolio holdings",
+      description: "One scheme's equity PORTFOLIO for a month (the stocks it holds) with month-over-month quantity change. The INVERSE of get_mutual_fund_holdings (which funds own a stock). schemeName must match the stored holdings name exactly, as returned by list_mutual_fund_portfolios \u2014 it is the scheme-NAME string, NOT the AMFI scheme_code. month is 'YYYY-MM' (latest if omitted). An unknown scheme name returns an empty portfolio, not an error.",
+      inputSchema: {
+        schemeName: z.string().describe("Holdings scheme name, exactly as returned by list_mutual_fund_portfolios."),
+        month: z.string().optional().describe("Portfolio month YYYY-MM. Latest if omitted."),
+        page: z.number().int().positive().optional(),
+        pageSize: z.number().int().positive().max(100).optional()
+      }
+    },
+    async ({ schemeName, month, page, pageSize }) => run(() => client.mutualFunds.getPortfolioHoldings(schemeName, { month, page, pageSize }))
+  );
   server.registerTool(
     "get_data_status",
     {

package/dist/http.js

@@ -2,7 +2,7 @@
 import {
   buildServer,
   checkAuthorization
-} from "./chunk-RPAWW7CN.js";
+} from "./chunk-LW5UFTIW.js";
 
 // src/http.ts
 import { randomUUID } from "crypto";

package/dist/index.d.ts

@@ -14,7 +14,7 @@ import { BharatStockOptions } from 'bharatstock';
  */
 
 declare const SERVER_NAME = "bharatstock";
-declare const SERVER_VERSION = "0.1.0";
+declare const SERVER_VERSION = "0.1.2";
 /**
  * Construct the MCP server and register all tools against a BharatStock
  * client. Exposed separately from the stdio wiring so tests can build a

package/dist/index.js

@@ -4,7 +4,7 @@ import {
   SERVER_VERSION,
   buildServer,
   checkAuthorization
-} from "./chunk-RPAWW7CN.js";
+} from "./chunk-LW5UFTIW.js";
 
 // src/index.ts
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bharatstock-mcp",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Official Model Context Protocol (MCP) server for the BharatStock API - reliable Indian stock market data (NSE/BSE) as AI-agent tools.",
   "license": "MIT",
   "type": "module",
@@ -35,7 +35,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.0",
-    "bharatstock": "^0.1.8",
+    "bharatstock": "^0.1.11",
     "zod": "^3.23.8"
   },
   "devDependencies": {