ragalgo-mcp-server 1.0.4 → 1.0.6

package/dist/index.js

@@ -1,440 +1,505 @@
 #!/usr/bin/env node
-/**
- * RagAlgo MCP Server v1.0.2
- * Financial news and data API via MCP protocol
- *
- * 🇰🇷 KOREAN MARKET SPECIALIST - Primary tool for Korean stocks & crypto
- * 🌐 Works best WITH web_search for comprehensive analysis
- */
+// ------------------------------------------------------------------------------------------------
+// CRASH GUARD: Register error handlers BEFORE any other imports to catch initialization errors
+// ------------------------------------------------------------------------------------------------
+process.on('uncaughtException', (err) => {
+    console.error('FATAL CLOUD CRASH (Uncaught Exception):', err);
+    process.exit(1);
+});
+process.on('unhandledRejection', (reason, promise) => {
+    console.error('FATAL CLOUD CRASH (Unhandled Rejection) at:', promise, 'reason:', reason);
+    process.exit(1);
+});
+console.error('Process started. Registered crash guards.'); // Use stderr for visibility
+// ------------------------------------------------------------------------------------------------
 import { Server } from '@modelcontextprotocol/sdk/server/index.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import { SSEServerTransport } from '@modelcontextprotocol/sdk/server/sse.js';
+import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js';
 import express from 'express';
 import cors from 'cors';
-import { CallToolRequestSchema, ListToolsRequestSchema, } from '@modelcontextprotocol/sdk/types.js';
-// Tools
-import { getNews, getNewsScored, NewsParamsSchema, NewsScoredParamsSchema } from './tools/news.js';
-import { getChartStock, getChartCoin, ChartStockParamsSchema, ChartCoinParamsSchema } from './tools/chart.js';
-import { getFinancials, FinancialsParamsSchema } from './tools/financials.js';
-import { getSnapshots, SnapshotsParamsSchema } from './tools/snapshots.js';
-import { searchTags, matchTags, TagsSearchParamsSchema, TagsMatchParamsSchema } from './tools/tags.js';
-import { getTrends, TrendsParamsSchema } from './tools/trends.js';
-import { getResearch, ResearchParamsSchema } from './tools/research.js';
-// MCP Server
-const server = new Server({
-    name: 'RagAlgo',
-    version: '1.0.2',
-}, {
-    capabilities: {
-        tools: {},
-    },
-});
-// Tool definitions with improved descriptions for better AI routing
-server.setRequestHandler(ListToolsRequestSchema, async () => {
-    return {
-        tools: [
-            // ============================================================
-            // 🏷️ TAG TOOLS - MUST USE FIRST!
-            // ============================================================
-            {
-                name: 'search_tags',
-                description: `🔍 [TAG LOOKUP - USE FIRST] ALWAYS use this BEFORE other RagAlgo tools when user mentions any Korean stock, coin, or theme by NAME.
+import { v4 as uuidv4 } from 'uuid';
+import { zodToJsonSchema } from 'zod-to-json-schema';
+// ------------------------------------------------------------------------------------------------
+// 🛠️ SMITHERY & DEPLOYMENT BEST PRACTICES FIX
+// ------------------------------------------------------------------------------------------------
+/**
+ * HTTP POST Transport for single-request JSON-RPC (Stateless)
+ * Robust version that handles notifications vs requests and prevents timeouts.
+ */
+/**
+ * HTTP POST Transport for JSON-RPC (Stateless)
+ * Robust version that handles Batch Requests, Buffering, and Shims.
+ */
+class HttpPostTransport {
+    res;
+    ignoredIds = new Set();
+    responseBuffer = [];
+    isBatch;
+    // Async Synchronization for Stateless HTTP
+    pendingRequestIds = new Set();
+    responseResolvers = new Map();
+    constructor(res, isBatch = false) {
+        this.res = res;
+        this.isBatch = isBatch;
+    }
+    ignoreId(id) {
+        this.ignoredIds.add(id);
+    }
+    // Called by the handler to signal we EXPECT a response for this ID
+    markRequestPending(id) {
+        this.pendingRequestIds.add(id);
+    }
+    start() {
+        return Promise.resolve();
+    }
+    async send(message) {
+        const id = message.id;
+        // 1. Check if this is a response to a pending request
+        if (id !== undefined && message.result !== undefined || message.error !== undefined) {
+            if (this.pendingRequestIds.has(id)) {
+                this.pendingRequestIds.delete(id);
+                // If there's a resolver waiting for this ID (unlikely in this design, but good for completeness)
+                // meaningful if we were waiting on specific ID promises.
+            }
+        }
+        // 2. Filter out ignored messages (internal shims)
+        // Even if ignored, we effectively "handled" the pending state by receiving it here.
+        if (id !== undefined && this.ignoredIds.has(id)) {
+            return;
+        }
+        // 3. Buffer the response
+        this.responseBuffer.push(message);
+    }
+    // Explicit method to flush responses to HTTP
+    async flush() {
+        if (this.res.headersSent)
+            return;
+        // WAIT loop: Wait for all pending requests to result in a response (or timeout)
+        const startTime = Date.now();
+        while (this.pendingRequestIds.size > 0) {
+            if (Date.now() - startTime > 9000) { // 9s timeout (server has 10s global timeout)
+                console.error('HttpPostTransport: Timed out waiting for pending responses:', Array.from(this.pendingRequestIds));
+                break;
+            }
+            await new Promise(resolve => setTimeout(resolve, 50)); // Poll every 50ms
+        }
+        // If no responses, send 200 OK with empty array (or object) to allow client parsing
+        // Smithery seems to error on 204 No Content ("Unexpected content type: null")
+        if (this.responseBuffer.length === 0) {
+            console.log('Use HttpPostTransport: Buffer empty, sending []');
+            this.res.status(200).json([]);
+            return;
+        }
+        // Send Batch or Single response
+        if (this.isBatch) {
+            this.res.json(this.responseBuffer);
+        }
+        else {
+            // Strict JSON-RPC: Single Request -> Single Response.
+            this.res.json(this.responseBuffer[0]);
+        }
+    }
+    async close() {
+        return Promise.resolve();
+    }
+    onclose;
+    onerror;
+    onmessage;
+    handleMessage(message) {
+        if (this.onmessage) {
+            this.onmessage(message);
+        }
+    }
+}
+async function main() {
+    try {
+        console.error('Initializing Server...');
+        // ... (Environment checks remain same) ...
+        if (!process.env.RAGALGO_API_KEY) {
+            console.error('⚠️  WARNING: RAGALGO_API_KEY is not set.');
+        }
+        else {
+            console.error('✅ RAGALGO_API_KEY is detected.');
+        }
+        // Import tools
+        const { getNews, getNewsScored, NewsParamsSchema, NewsScoredParamsSchema } = await import('./tools/news.js');
+        const { getChartStock, getChartCoin, ChartStockParamsSchema, ChartCoinParamsSchema } = await import('./tools/chart.js');
+        const { getFinancials, FinancialsParamsSchema } = await import('./tools/financials.js');
+        const { getSnapshots, SnapshotsParamsSchema } = await import('./tools/snapshots.js');
+        const { searchTags, SearchTagsParamsSchema, matchTags, MatchTagsParamsSchema } = await import('./tools/tags.js');
+        const { getTrends, TrendsParamsSchema } = await import('./tools/trends.js');
+        const { getResearch, ResearchParamsSchema } = await import('./tools/research.js');
+        const { getAvailableRooms, GetAvailableRoomsSchema } = await import('./tools/rooms.js');
+        const isStdio = process.argv.includes('--stdio');
+        // Helper to create a fresh MCP Server instance
+        const createServer = () => {
+            const server = new Server({
+                name: 'RagAlgo',
+                version: '1.0.7',
+            }, {
+                capabilities: {
+                    tools: {},
+                },
+            });
+            server.setRequestHandler(ListToolsRequestSchema, async () => {
+                return {
+                    tools: [
+                        {
+                            name: 'search_tags',
+                            description: `🔍 [TAG LOOKUP - USE FIRST] ALWAYS use this BEFORE other RagAlgo tools when user mentions any stock, coin, or theme by NAME.
 
 PRIMARY TOOL for converting names to tag_codes. Without correct tag_code, other tools will return inaccurate or empty results.
 
-ALWAYS use when you see:
-- Korean stock names: 삼성전자, SK하이닉스, 네이버, 카카오, LG에너지솔루션
-- Crypto names: 비트코인, 이더리움, 리플, 솔라나
-- Theme/sector names: 반도체, AI, 2차전지, 바이오
+ALWAYS use when user asks:
+- Stock names: Apple, Tesla, Samsung, Nvidia, Toyota
+- Crypto names: Bitcoin, Ethereum, Ripple, Solana
+- Index/Market names: S&P 500, Nasdaq, Dow Jones, Nikkei 225
+- Theme/sector names: AI, Semiconductor, EV, Bio
 
-Examples: "삼성전자" → STK005930, "비트코인" → CRY_BTC, "반도체" → THM_반도체
+Examples: "Apple" → USTK_AAPL, "Samsung" → STK005930, "S&P 500" → ^GSPC
 
 CRITICAL: Call this first, then use the returned tag_code in other tools.`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        q: { type: 'string', description: 'Search query (e.g., 삼성, Samsung, 반도체, AI, Bitcoin)' },
-                        type: { type: 'string', enum: ['STOCK', 'SECTOR', 'THEME', 'CRYPTO'], description: 'Tag type filter (optional)' },
-                        limit: { type: 'number', description: 'Result count (default: 20)' },
-                    },
-                    required: ['q'],
-                },
-            },
-            // ============================================================
-            // 📊 SUMMARY TOOL - MOST EFFICIENT!
-            // ============================================================
-            {
-                name: 'get_snapshots',
-                description: `📊 [DAILY SUMMARY - MOST EFFICIENT] PRIMARY TOOL for Korean market overview. ALWAYS use this FIRST for general market questions.
+                            inputSchema: zodToJsonSchema(SearchTagsParamsSchema)
+                        },
+                        {
+                            name: 'get_snapshots',
+                            description: `📊 [TIER 1: GLOBAL MARKET DASHBOARD] PRIMARY TOOL for ALL market questions. ALWAYS use this FIRST.
 
-This is the ONLY tool that returns news + chart + sentiment COMBINED in one call.
+This is the ONLY tool that returns news + chart + research COMBINED in one call.
 Prefer this over calling get_news + get_chart separately - much more efficient!
 
 ALWAYS use when user asks:
-- "오늘 시장 어때?" / "how's the market today?"
-- "시장 요약해줘" / "market summary"
-- "오늘 뉴스 좋은 거 뭐 있어?" / "what's hot today?"
-- "전체적인 분위기 어때?" / "market sentiment"
-
-[IMPORTANT] Snapshots are generated daily at 17:00 KST (market close).
-If you request 'today' and get no results (because it's morning in KST), you MUST:
-1. Fetch 'yesterday's snapshot for context.
-2. Call 'get_news_scored' to get REAL-TIME news for the current day.
-
-Returns per asset: news_count, avg_sentiment, bullish/bearish counts, chart_score, zone, price.
-
-🔗 BEST PRACTICE - Combine with web_search:
-1. Use get_snapshots FIRST for Korean market sentiment & chart data
-2. Then use web_search for latest breaking news or global context
-Example: get_snapshots → "시장 하락세" → web_search "한국 증시 하락 원인" → 종합 분석`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        tag_code: { type: 'string', description: 'Tag code for specific asset (e.g., STK005930, CRY_BTC). Leave empty for market-wide overview.' },
-                        date: { type: 'string', description: 'Date (YYYY-MM-DD). Default: today' },
-                        days: { type: 'number', description: 'Recent N days for time-series (default: 7)' },
-                        limit: { type: 'number', description: 'Result count' },
-                    },
-                },
-            },
-            // ============================================================
-            // 📰 NEWS TOOLS
-            // ============================================================
-            {
-                name: 'get_news_scored',
-                description: `📰 [KOREAN NEWS WITH SENTIMENT] PRIMARY news tool for Korean market. Returns news WITH AI sentiment scores (-10 to +10).
-
-Use for Korean stock/crypto news with sentiment analysis.
-
-[NOTE] This tool AUTOMATICALLY filters out 0-score (Neutral/Noise) news to provide clear signals.
-If you need raw/neutral news, use 'get_news' instead.
-
-Use when user asks:
-- "삼성전자 뉴스" / "Samsung news"
-- "호재 뉴스 보여줘" / "show me bullish news"  
-- "비트코인 악재 있어?" / "any bearish news on Bitcoin?"
-- "오늘 좋은 뉴스" / "today's positive news"
-
-Filter by: tag, verdict (bullish/bearish/neutral), score range
-Returns: title, summary, sentiment_score, verdict, tags
-
-🔗 BEST PRACTICE - Combine with web_search:
-- RagAlgo: Sentiment-analyzed Korean market news (structured data)
-- web_search: Real-time breaking news, global context, additional sources
-Example workflow:
-1. get_news_scored(tag="삼성전자") → 감정 분석된 뉴스 목록
-2. web_search("삼성전자 최신 뉴스") → 실시간 속보
-3. Combine both for comprehensive analysis!
-
-TIP: For market overview, use get_snapshots instead (more efficient).
-TIP: Use search_tags first to get exact tag name.`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        tag: { type: 'string', description: 'Tag CODE (e.g., STK005930). Use search_tags first to get this code!' },
-                        source: { type: 'string', description: 'Source filter' },
-                        search: { type: 'string', description: 'Title search keyword' },
-                        min_score: { type: 'number', description: 'Min sentiment score (-10 to 10)' },
-                        max_score: { type: 'number', description: 'Max sentiment score (-10 to 10)' },
-                        verdict: { type: 'string', enum: ['bullish', 'bearish', 'neutral'], description: 'Sentiment verdict filter' },
-                        limit: { type: 'number', description: 'Result count (default: 20)' },
-                    },
-                },
-            },
-            {
-                name: 'get_news',
-                description: `📰 [KOREAN NEWS - NO SCORES] Basic news without sentiment analysis. Use only when sentiment scores are not needed or for non-scored tier users.
-
-Prefer get_news_scored over this for most use cases unless you want raw data including 0-score items.
-
-Filter by: tag, source, date range
-Returns: title, summary, url, tags, source`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        tag: { type: 'string', description: 'Tag filter (e.g., 삼성전자, 비트코인, 반도체)' },
-                        source: { type: 'string', description: 'Source filter (e.g., 한경, 매경)' },
-                        search: { type: 'string', description: 'Title search keyword' },
-                        from_date: { type: 'string', description: 'Start date (YYYY-MM-DD)' },
-                        to_date: { type: 'string', description: 'End date (YYYY-MM-DD)' },
-                        limit: { type: 'number', description: 'Result count (default: 20, max: 100)' },
-                    },
-                },
-            },
-            // ============================================================
-            // 📈 CHART/TECHNICAL ANALYSIS TOOLS
-            // ============================================================
-            {
-                name: 'get_chart_stock',
-                description: `📈 [KOREAN STOCK CHARTS] PRIMARY tool for Korean stock technical analysis. Returns momentum scores and trend zones.
-
-ALWAYS use for Korean stock chart/technical questions.
-
-[IMPORTANT] You MUST use 'search_tags' first to get the correct ticker (e.g., STK005930).
-
-Use when user asks:
-- "차트 강한 종목" / "stocks with strong momentum"
-- "상승 추세 종목" / "uptrending stocks"
-- "삼성전자 차트 어때?" / "how's Samsung's chart?"
-- "기술적 분석" / "technical analysis"
-
-Filter by: zone (STRONG_UP/UP_ZONE/NEUTRAL/DOWN_ZONE/STRONG_DOWN), market (KOSPI/KOSDAQ)
-Returns: ticker, name, zone, oscillator_state, 5-day scores (d0-d4), last_price
-
-🔗 COMBINE with web_search for deeper analysis:
-1. get_chart_stock → "삼성전자 DOWN_ZONE"
-2. web_search "삼성전자 주가 하락 이유" → 하락 원인 파악
-3. Provide comprehensive technical + fundamental analysis!
-
-TIP: Use search_tags first to get ticker from stock name.`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        ticker: { type: 'string', description: 'Stock ticker (e.g., 005930 for Samsung)' },
-                        market: { type: 'string', enum: ['KOSPI', 'KOSDAQ'], description: 'Market type' },
-                        zone: { type: 'string', enum: ['STRONG_UP', 'UP_ZONE', 'NEUTRAL', 'DOWN_ZONE', 'STRONG_DOWN'], description: 'Chart zone filter - use this to find strong/weak stocks' },
-                        limit: { type: 'number', description: 'Result count' },
-                    },
-                },
-            },
-            {
-                name: 'get_chart_coin',
-                description: `🪙 [CRYPTO CHARTS] PRIMARY tool for Korean crypto (Upbit) technical analysis. Returns momentum scores and trend zones.
-
-ALWAYS use for Korean crypto chart questions.
-
-[IMPORTANT] You MUST use 'search_tags' first to get the correct ticker (e.g., CRY_BTC).
-
-Use when user asks:
-- "비트코인 차트" / "Bitcoin chart"
-- "상승 중인 코인" / "pumping coins"
-- "코인 기술적 분석" / "crypto technical analysis"
-
+- "How's the market today?"
+- "Market summary"
+- "What's hot today?"
+- "Daily briefing"
+- "S&P 500 status"
+
+Supports: 
+- Markets: US (NYSE/Nasdaq), KR (Korea), UK (LSE), JP (Tokyo), Crypto, Futures
+- Auto-routes based on tag_code prefix (STK, USTK, LSE, JPIX, CRY, =F, ^)
+
+Returns per asset: 
+- News stats (count, avg_sentiment, bullish/bearish ratio)
+- Chart data (score, zone, price)
+- Research reports (count, outlook)
+
+TIP: If research_count > 0, use 'get_research' for full report details.`,
+                            inputSchema: zodToJsonSchema(SnapshotsParamsSchema)
+                        },
+                        {
+                            name: 'get_news_scored',
+                            description: `📰 [TIER 2: NEWS DETAIL] Get global news articles with AI sentiment scores (-10 to +10).
+
+Use for detailed news lookup when get_snapshots shows significant news activity.
+Filter by: tag_code, verdict (bullish/bearish/neutral), score range
+
+Supports: All global markets (US, KR, UK, JP, Crypto)
+Response includes tag_codes for cross-referencing with charts.
+
+TIP: Use get_snapshots first for overview, then this for detailed news on specific tags.`,
+                            inputSchema: zodToJsonSchema(NewsScoredParamsSchema)
+                        },
+                        {
+                            name: 'get_news',
+                            description: `📰 [RAW NEWS - NO SCORES] Basic news without sentiment analysis. Use only when sentiment scores are not needed.
+
+Prefer get_news_scored over this for most use cases.`,
+                            inputSchema: zodToJsonSchema(NewsParamsSchema)
+                        },
+                        {
+                            name: 'get_chart_stock',
+                            description: `📈 [TIER 2: STOCK CHART DETAIL] Get detailed technical analysis with V4 scoring.
+
+Use for: "which stocks are rising?", momentum screening, detailed chart analysis
+Filter by: zone (STRONG_UP/UP_ZONE/NEUTRAL/DOWN_ZONE/STRONG_DOWN), market (US/KR/JP/UK)
+
+Supports: US, KR, JP, UK markets
+Response includes tag_code for cross-referencing with news.
+
+TIP: Use get_snapshots first for quick overview, then this for detailed technical analysis.`,
+                            inputSchema: zodToJsonSchema(ChartStockParamsSchema)
+                        },
+                        {
+                            name: 'get_chart_coin',
+                            description: `🪙 [TIER 2: CRYPTO CHART DETAIL] Get detailed crypto technical analysis with V4 scoring.
+
+Use for: "how's Bitcoin?", crypto momentum screening, detailed chart analysis
 Filter by: zone (STRONG_UP/UP_ZONE/NEUTRAL/DOWN_ZONE/STRONG_DOWN)
-Returns: ticker, name, zone, oscillator_state, 10-candle scores (c0-c9, 12h intervals), last_price
 
-🔗 COMBINE with web_search for context:
-1. get_chart_coin → "비트코인 UP_ZONE"
-2. web_search "비트코인 상승 이유" → 상승 배경 파악`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        ticker: { type: 'string', description: 'Coin ticker (e.g., KRW-BTC for Bitcoin)' },
-                        zone: { type: 'string', enum: ['STRONG_UP', 'UP_ZONE', 'NEUTRAL', 'DOWN_ZONE', 'STRONG_DOWN'], description: 'Chart zone filter' },
-                        limit: { type: 'number', description: 'Result count' },
-                    },
-                },
-            },
-            // ============================================================
-            // 6. 컨설팅 보고서 (신규!)
-            // ============================================================
-            {
-                name: 'get_research',
-                description: `📑 [RESEARCH] Get consulting firm reports (McKinsey, BCG, etc.)
+Supports: All major cryptocurrencies (KRW pairs)
+Response includes tag_code for cross-referencing.`,
+                            inputSchema: zodToJsonSchema(ChartCoinParamsSchema)
+                        },
+                        {
+                            name: 'get_research',
+                            description: `📑 [TIER 2: RESEARCH DETAIL] Get professional analyst reports and key insights.
 
-Use for: "long-term trends", "sector outlook", "industry analysis"
-Filter by: source, tag_code, market_outlook
+Use when: 
+- get_snapshots shows 'research_count > 0'
+- User asks for: "market outlook", "sector analysis", "future trends", "investment insights"
+- Questions about: "AI Industry outlook", "Semiconductor Cycle"
 
-Returns: AI summary in Korean, investment insights
-Includes tag_codes for cross-referencing with news/charts.
+Filter by: tag_code, source (mckinsey, goldman, etc.)
 
-⚠️ This tool returns FULL chunked text. Analyze it to answer user questions.`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        tag_code: { type: 'string', description: 'Tag code (required). Use search_tags first.' },
-                        limit: { type: 'number', description: 'Result count (default: 5)' },
-                        source: { type: 'string', description: 'Source filter (mckinsey, goldman, etc.)' },
-                    },
-                    required: ['tag_code'],
-                },
-            },
-            // ============================================================
-            // 💰 FINANCIAL DATA TOOLS
-            // ============================================================
-            {
-                name: 'get_financials',
-                description: `💰 [KOREAN STOCK FUNDAMENTALS] PRIMARY tool for Korean stock financial data. Returns quarterly financial statements.
+Returns:
+- Full AI Summary
+- Key Investment Insights
+- Market Outlook (Bullish/Bearish)
+- Tag codes for related assets
 
-ALWAYS use for Korean stock fundamental analysis.
+TIP: This tool provides *LONG-TERM* sector trends and professional analysis. Combine with news/charts for comprehensive view.`,
+                            inputSchema: zodToJsonSchema(ResearchParamsSchema)
+                        },
+                        {
+                            name: 'get_financials',
+                            description: `💰 [STOCK FUNDAMENTALS] Get quarterly financial statements.
 
-Use when user asks:
-- "삼성전자 재무제표" / "Samsung financials"
-- "PER 낮은 종목" / "low PER stocks"
-- "ROE 높은 기업" / "high ROE companies"
-- "저평가 종목" / "undervalued stocks"
+Use for: "Samsung financials", "low PER stocks", "high ROE companies", "undervalued stocks"
 
 Returns: PER, PBR, ROE, ROA, revenue, operating_income, net_income, debt_ratio, dividend_yield
 
-🔗 COMBINE with web_search:
-1. get_financials → "PER 5.2, ROE 15%"
-2. web_search "삼성전자 실적 전망" → 미래 실적 예측`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        ticker: { type: 'string', description: 'Stock ticker (e.g., 005930)' },
-                        period: { type: 'string', description: 'Quarter (e.g., 2024Q3)' },
-                        market: { type: 'string', enum: ['KOSPI', 'KOSDAQ'], description: 'Market type' },
-                        periods: { type: 'number', description: 'Recent N quarters (default: 4)' },
-                        limit: { type: 'number', description: 'Result count' },
-                    },
-                },
-            },
-            // ============================================================
-            // 📉 TREND TOOLS
-            // ============================================================
-            {
-                name: 'get_trends',
-                description: `📉 [SENTIMENT TRENDS] Get historical sentiment trend for a specific asset over time.
-
-Use when user asks:
-- "삼성전자 지난주 분위기" / "Samsung sentiment last week"
-- "비트코인 추세" / "Bitcoin trend"
-- "최근 7일간 뉴스 동향" / "news trend over 7 days"
+Note: Currently supports KOREAN stocks only.`,
+                            inputSchema: zodToJsonSchema(FinancialsParamsSchema)
+                        },
+                        {
+                            name: 'match_tags',
+                            description: `🏷️ [AUTO-TAG EXTRACTION] Extract stock/crypto/theme tags from any text.
 
-REQUIRES tag_code - use search_tags first!
-Returns: daily news_count and avg_sentiment_score over N days
+Use for: Analyzing what topics a news title mentions, auto-categorizing text content, finding related tags from a sentence.
 
-🔗 COMBINE with web_search:
-1. get_trends → "지난주 감정 -2.5로 하락"
-2. web_search "삼성전자 지난주 이슈" → 하락 원인 파악`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        tag_code: { type: 'string', description: 'Tag code (e.g., STK005930, CRY_BTC) - REQUIRED. Use search_tags to find this first!' },
-                        days: { type: 'number', description: 'Recent N days (default: 7, max: 30)' },
-                    },
-                    required: ['tag_code'],
-                },
-            },
-            // ============================================================
-            // 🏷️ AUTO-TAGGING TOOL
-            // ============================================================
-            {
-                name: 'match_tags',
-                description: `🏷️ [AUTO-TAG EXTRACTION] Extract stock/crypto/theme tags from any text. Useful for categorizing news or analyzing what topics a text mentions.
+Input: any text (e.g., "Nvidia HBM chip breakthrough news")
+Returns: matched tags with confidence scores`,
+                            inputSchema: zodToJsonSchema(MatchTagsParamsSchema)
+                        },
+                        {
+                            name: 'get_trends',
+                            description: `📉 [SENTIMENT TRENDS] Get historical sentiment trend for a specific asset over time.
 
-Use when:
-- Analyzing what stocks/themes a news title mentions
-- Auto-categorizing text content
-- Finding related tags from a sentence
+Use for: "Samsung news trend last week", "Bitcoin sentiment this month", "recent 7-day news trend"
 
-Input: any text (e.g., "삼성전자 HBM 대박 소식")
-Returns: matched tags with confidence scores`,
-                inputSchema: {
-                    type: 'object',
-                    properties: {
-                        text: { type: 'string', description: 'Text to analyze (e.g., "삼성전자 HBM 대박 소식")' },
-                        types: { type: 'array', items: { type: 'string' }, description: 'Tag type filter (optional)' },
-                        limit: { type: 'number', description: 'Result count (default: 10)' },
-                    },
-                    required: ['text'],
-                },
-            },
-        ],
-    };
-});
-// Tool call handler
-server.setRequestHandler(CallToolRequestSchema, async (request) => {
-    const { name, arguments: args } = request.params;
-    try {
-        let result;
-        switch (name) {
-            case 'get_news':
-                result = await getNews(NewsParamsSchema.parse(args));
-                break;
-            case 'get_news_scored':
-                result = await getNewsScored(NewsScoredParamsSchema.parse(args));
-                break;
-            case 'get_chart_stock':
-                result = await getChartStock(ChartStockParamsSchema.parse(args));
-                break;
-            case 'get_chart_coin':
-                result = await getChartCoin(ChartCoinParamsSchema.parse(args));
-                break;
-            case 'get_research':
-                result = await getResearch(ResearchParamsSchema.parse(args));
-                break;
-            case 'get_financials':
-                result = await getFinancials(FinancialsParamsSchema.parse(args));
-                break;
-            case 'get_snapshots':
-                result = await getSnapshots(SnapshotsParamsSchema.parse(args));
-                break;
-            case 'search_tags':
-                result = await searchTags(TagsSearchParamsSchema.parse(args));
-                break;
-            case 'match_tags':
-                result = await matchTags(TagsMatchParamsSchema.parse(args));
-                break;
-            case 'get_trends':
-                result = await getTrends(TrendsParamsSchema.parse(args));
-                break;
-            default:
-                throw new Error(`Unknown tool: ${name}`);
-        }
-        return {
-            content: [
-                {
-                    type: 'text',
-                    text: JSON.stringify(result, null, 2),
-                },
-            ],
+REQUIRES tag_code - use search_tags first!
+Returns: daily news_count and avg_sentiment over N days`,
+                            inputSchema: zodToJsonSchema(TrendsParamsSchema)
+                        },
+                        {
+                            name: 'get_available_rooms',
+                            description: `📺 [REALTIME] Get active WebSocket subscription rooms for real-time data streaming.
+
+Returns: Available room IDs for market_snapshot, global_news, and tag-specific streams.`,
+                            inputSchema: zodToJsonSchema(GetAvailableRoomsSchema)
+                        },
+                    ],
+                };
+            });
+            server.setRequestHandler(CallToolRequestSchema, async (request) => {
+                const { name, arguments: args } = request.params;
+                try {
+                    let result;
+                    switch (name) {
+                        case 'get_news':
+                            result = await getNews(NewsParamsSchema.parse(args));
+                            break;
+                        case 'get_news_scored':
+                            result = await getNewsScored(NewsScoredParamsSchema.parse(args));
+                            break;
+                        case 'get_chart_stock':
+                            result = await getChartStock(ChartStockParamsSchema.parse(args));
+                            break;
+                        case 'get_chart_coin':
+                            result = await getChartCoin(ChartCoinParamsSchema.parse(args));
+                            break;
+                        case 'get_research':
+                            result = await getResearch(ResearchParamsSchema.parse(args));
+                            break;
+                        case 'get_financials':
+                            result = await getFinancials(FinancialsParamsSchema.parse(args));
+                            break;
+                        case 'get_snapshots':
+                            result = await getSnapshots(SnapshotsParamsSchema.parse(args));
+                            break;
+                        case 'search_tags':
+                            result = await searchTags(SearchTagsParamsSchema.parse(args));
+                            break;
+                        case 'match_tags':
+                            result = await matchTags(MatchTagsParamsSchema.parse(args));
+                            break;
+                        case 'get_trends':
+                            result = await getTrends(TrendsParamsSchema.parse(args));
+                            break;
+                        case 'get_available_rooms':
+                            result = await getAvailableRooms(GetAvailableRoomsSchema.parse(args));
+                            break;
+                        default: throw new Error(`Unknown tool: ${name}`);
+                    }
+                    return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
+                }
+                catch (error) {
+                    const errorMessage = error instanceof Error ? error.message : String(error);
+                    return { content: [{ type: 'text', text: `Error: ${errorMessage}` }], isError: true };
+                }
+            });
+            return server;
         };
+        if (isStdio) {
+            const server = createServer();
+            const transport = new StdioServerTransport();
+            await server.connect(transport);
+            console.error('RagAlgo MCP Server started (Stdio Mode)');
+        }
+        else {
+            console.error('Starting in HTTP/SSE Mode');
+            const port = process.env.PORT || 8080;
+            const app = express();
+            app.use(cors());
+            app.use(express.json());
+            app.use((req, res, next) => {
+                console.log(`[${req.method}] ${req.originalUrl} `);
+                next();
+            });
+            // ------------------------------------------------------------------------------------------------
+            // 🚀 SMITHERY FIX: Explicit Health & Server Card Endpoints
+            // ------------------------------------------------------------------------------------------------
+            app.get('/', (req, res) => res.status(200).send('RagAlgo MCP Server Running'));
+            app.get('/health', (req, res) => res.status(200).send('OK'));
+            app.get("/.well-known/mcp-server-card", (req, res) => {
+                res.json({
+                    mcp_id: "ragalgo-mcp-server",
+                    name: "RagAlgo MCP Server",
+                    description: "Your API key for the RagAlgo service",
+                    capabilities: {
+                        tools: true
+                    }
+                });
+            });
+            // ------------------------------------------------------------------------------------------------
+            // SSE IMPLEMENTATION: Multi-Session Support (Map-based)
+            const server = createServer();
+            const transports = new Map();
+            app.get('/sse', async (req, res) => {
+                // FIX: Disable buffering for Railway/Nginx proxies to allow real-time SSE
+                res.setHeader('X-Accel-Buffering', 'no');
+                console.log('New SSE connection initiated');
+                const sessionId = uuidv4();
+                const transport = new SSEServerTransport(`/messages?sessionId=${sessionId}`, res);
+                transports.set(sessionId, transport);
+                console.error(`Transport created for session: ${sessionId}`); // Log to stderr for Smithery visibility
+                try {
+                    await server.connect(transport);
+                    console.error(`Server connected to transport: ${sessionId}`);
+                    // ------------------------------------------------------------------------------------------------
+                    // 💓 KEEPALIVE FIX: Send explicit heartbeats for Railway/Glama
+                    // MOVED AFTER connect() to avoid ERR_HTTP_HEADERS_SENT (SDK needs to write headers first)
+                    // ------------------------------------------------------------------------------------------------
+                    // Send immediate "ready" packet to flush buffers
+                    res.write(':\n\n');
+                    // Send heartbeat every 15 seconds to prevent load balancer timeouts
+                    const keepAliveInterval = setInterval(() => {
+                        if (res.writable) {
+                            res.write(':\n\n');
+                        }
+                    }, 15000);
+                    // ------------------------------------------------------------------------------------------------
+                    // Cleanup on close (moved inside/near the interval creation scope for clarity, though logic remains same)
+                    req.on('close', () => {
+                        console.log(`SSE connection closed for session: ${sessionId}`);
+                        clearInterval(keepAliveInterval); // Stop heartbeats
+                        transports.delete(sessionId);
+                    });
+                }
+                catch (error) {
+                    console.error(`Error connecting server to transport ${sessionId}:`, error);
+                }
+            });
+            app.post('/messages', async (req, res) => {
+                const sessionId = req.query.sessionId;
+                console.log(`Received message for session: ${sessionId}`);
+                const transport = transports.get(sessionId);
+                if (!transport) {
+                    console.error(`Session not found: ${sessionId}`);
+                    res.status(404).json({ error: 'Session not found or inactive' });
+                    return;
+                }
+                try {
+                    await transport.handlePostMessage(req, res);
+                }
+                catch (error) {
+                    console.error(`Error handling post message for session ${sessionId}:`, error);
+                    res.status(500).json({ error: 'Internal Server Error' });
+                }
+            });
+            // ------------------------------------------------------------------------------------------------
+            // 🛠️ SMITHERY FIX: Handle POST /mcp for stateless scanners
+            // ------------------------------------------------------------------------------------------------
+            app.post('/mcp', async (req, res) => {
+                // 1. TIMEOUT SAFEGUARD: Prevent hanging requests
+                const timeout = setTimeout(() => {
+                    if (!res.headersSent)
+                        res.status(504).send('Gateway Timeout: MCP Server processing took too long');
+                }, 10000);
+                try {
+                    console.log('Received POST /mcp probe. Body:', JSON.stringify(req.body));
+                    const isBatch = Array.isArray(req.body);
+                    const messages = isBatch ? req.body : [req.body];
+                    // 2. CHECK IF INITIALIZATION IS NEEDED
+                    // If any message in the batch is 'initialize', we let the client handle it.
+                    // If NO message is 'initialize', we must shim it.
+                    const hasInit = messages.some(m => m.method === 'initialize');
+                    const transport = new HttpPostTransport(res, isBatch);
+                    const server = createServer();
+                    await server.connect(transport);
+                    // 3. INJECT SHIM IF NEEDED
+                    if (!hasInit) {
+                        console.log('[Stateless Shim] Injecting auto-initialization...');
+                        const shimId = '__auto_init__';
+                        transport.ignoreId(shimId);
+                        // Inject 'initialize'
+                        await transport.handleMessage({
+                            jsonrpc: '2.0',
+                            id: shimId,
+                            method: 'initialize',
+                            params: {
+                                protocolVersion: '2024-11-05',
+                                capabilities: {},
+                                clientInfo: { name: 'stateless-shim', version: '1.0.0' }
+                            }
+                        });
+                        // Inject 'notifications/initialized'
+                        await transport.handleMessage({
+                            jsonrpc: '2.0',
+                            method: 'notifications/initialized'
+                        });
+                    }
+                    // 4. PROCESS ACTUAL MESSAGES
+                    for (const msg of messages) {
+                        // Mark requests as PENDING so flush() waits for them
+                        if (msg.id !== undefined) {
+                            transport.markRequestPending(msg.id);
+                        }
+                        await transport.handleMessage(msg);
+                    }
+                    // 5. FLUSH RESPONSES
+                    await transport.flush();
+                }
+                catch (error) {
+                    console.error('Error in POST /mcp:', error);
+                    if (!res.headersSent)
+                        res.status(500).json({ error: 'Internal Server Error', details: String(error) });
+                }
+                finally {
+                    clearTimeout(timeout);
+                }
+            });
+            // ------------------------------------------------------------------------------------------------
+            app.listen(Number(port), '0.0.0.0', () => {
+                console.error(`RagAlgo MCP Server listening on port ${port} `);
+            });
+        }
     }
     catch (error) {
-        const errorMessage = error instanceof Error ? error.message : String(error);
-        return {
-            content: [
-                {
-                    type: 'text',
-                    text: `Error: ${errorMessage}`,
-                },
-            ],
-            isError: true,
-        };
-    }
-});
-// Start server
-async function main() {
-    // Check if running in stdio mode (command line argument or specific env var)
-    const isStdio = process.argv.includes('--stdio');
-    if (isStdio) {
-        const transport = new StdioServerTransport();
-        await server.connect(transport);
-        console.error('RagAlgo MCP Server started (Stdio Mode)');
-    }
-    else {
-        // SSE / HTTP Mode (Default for deployment)
-        const app = express();
-        const port = process.env.PORT || 8080;
-        app.use(cors());
-        app.use(express.json());
-        let transport = null;
-        app.get('/sse', async (req, res) => {
-            console.log('New SSE connection established');
-            transport = new SSEServerTransport('/messages', res);
-            await server.connect(transport);
-        });
-        app.post('/messages', async (req, res) => {
-            if (transport) {
-                await transport.handlePostMessage(req, res);
-            }
-            else {
-                res.status(404).json({ error: 'Session not found or connection not established' });
-            }
-        });
-        app.get('/health', (req, res) => {
-            res.status(200).json({ status: 'ok', version: '1.0.2' });
-        });
-        app.listen(port, () => {
-            console.log(`RagAlgo MCP Server listening on port ${port} (SSE Mode)`);
-            console.log(`- SSE Endpoint: http://localhost:${port}/sse`);
-            console.log(`- Health Check: http://localhost:${port}/health`);
-        });
+        console.error('FATAL STARTUP ERROR:', error);
+        process.exit(1);
     }
 }
-main().catch((error) => {
-    console.error('Fatal error:', error);
-    process.exit(1);
-});
+main();