Skip to main content
Glama
deenesjakoruzh
Cognitive-Stack

Search Stock News MCP Server

by Cognitive-Stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

🔌 Cline, Cursor, Claude Desktop 및 기타 MCP 클라이언트와 호환됩니다!

주식 뉴스 검색 MCP는 모든 MCP 클라이언트와 원활하게 작동합니다.

MCP(Model Context Protocol)는 AI 시스템이 다양한 데이터 소스 및 도구와 원활하게 상호 작용할 수 있도록 하는 개방형 표준으로, 안전한 양방향 연결을 용이하게 합니다.

Search Stock News MCP 서버는 다음을 제공합니다.

  • Tavily API를 통한 실시간 주식 뉴스 검색 기능

  • 다양한 사용자 정의 검색 쿼리 템플릿

  • 구성 가능한 검색 매개변수 및 필터링

  • 도메인별 콘텐츠 필터링

  • TypeScript를 사용한 유형 안전 작업

필수 조건 🔧

시작하기 전에 다음 사항을 확인하세요.

  • 타빌리 API 키

  • Claude Desktop, Cursor 또는 MCP 호환 클라이언트

  • Node.js(v16 이상)

  • Git 설치됨(Git 설치 방법을 사용하는 경우에만 필요)

Related MCP server: Tavily News Search MCP Server

주식 뉴스 검색 MCP 서버 설치 ⚡

NPX로 실행

지엑스피1

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Search Stock News MCP Server를 자동으로 설치하려면:

npx -y @smithery/cli install search-stock-news-mcp --client claude

MCP 클라이언트 구성 ⚙️

Cline 구성 🤖

클라인에서 Search Stock News MCP 서버를 설정하는 가장 쉬운 방법은 마켓플레이스를 이용하는 것입니다.

  1. VS Code에서 Cline 열기

  2. 사이드바에서 Cline 아이콘을 클릭하세요

  3. "MCP 서버" 탭으로 이동합니다.

  4. "주식뉴스검색"을 검색 후 "설치"를 클릭하세요.

  5. 메시지가 표시되면 Tavily API 키를 입력하세요.

또는 Cline에서 서버를 수동으로 구성하세요.

  1. Cline MCP 설정 파일을 엽니다.

# For macOS:
code ~/Library/Application\ Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

# For Windows:
code %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json

  1. 주식 뉴스 검색 서버 구성을 추가합니다.

{
  "mcpServers": {
    "search-stock-news-mcp": {
      "command": "npx",
      "args": ["-y", "search-stock-news-mcp@latest"],
      "env": {
        "TAVILY_API_KEY": "your-api-key-here"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

커서 구성 🖥️

Cursor에서 Search Stock News MCP 서버를 설정하려면:

  1. 커서 설정 열기

  2. 기능 > MCP 서버로 이동

  3. "+ 새 MCP 서버 추가" 버튼을 클릭하세요

  4. 다음 정보를 입력하세요:

    • 이름 : "search-stock-news-mcp"

    • 유형 : "명령"

    • 명령어 : GXP5

Claude Desktop 구성하기 🖥️

macOS의 경우:

touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

Windows의 경우:

code %APPDATA%\Claude\claude_desktop_config.json

서버 구성을 추가합니다.

{
  "mcpServers": {
    "search-stock-news-mcp": {
      "command": "npx",
      "args": ["-y", "search-stock-news-mcp@latest"],
      "env": {
        "TAVILY_API_KEY": "your-api-key-here"
      }
    }
  }
}

사용 예시 🎯

  1. 기본 주식 뉴스 검색 :

{
  "symbol": "AAPL",
  "companyName": "Apple Inc.",
  "maxResults": 10
}

  1. 필터를 사용한 고급 검색 :

{
  "symbol": "TSLA",
  "companyName": "Tesla Inc.",
  "maxResults": 20,
  "searchDepth": "advanced",
  "minScore": 0.6
}

  1. 사용자 정의 도메인 검색 :

{
  "symbol": "MSFT",
  "companyName": "Microsoft Corporation",
  "includeDomains": ["reuters.com", "bloomberg.com"]
}

문제 해결 🛠️

일반적인 문제

  1. 서버를 찾을 수 없습니다

    • npm 설치 확인

    • 구성 구문 확인

    • Node.js가 제대로 설치되었는지 확인하세요

  2. API 키 문제

    • Tavily API 키가 유효한지 확인하세요

    • 구성에서 API 키가 올바르게 설정되었는지 확인하세요.

    • API 키 주위에 공백이나 따옴표가 없는지 확인하세요.

  3. 검색 결과 문제

    • 검색 매개변수가 유효한 범위 내에 있는지 확인하세요.

    • 도메인 필터가 올바르게 형식화되었는지 확인하세요

    • 회사 이름과 상징이 정확한지 확인하세요

감사의 말 ✨

  • MCP 사양을 위한 모델 컨텍스트 프로토콜

  • 클로드 데스크탑을 위한 인류학

  • 뉴스 검색 API를 위한 Tavily

특허

MIT

Available Tools

2 tools
search-stock-newsC

Search for stock-related news using Tavily API

ParametersJSON Schema
NameRequiredDescriptionDefault
companyNameYesCompany name (e.g., Apple Inc.)
maxResultsNoMaximum number of results to return
minScoreNoMinimum relevance score threshold
searchDepthNoSearch depth level
symbolYesStock symbol (e.g., AAPL)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the Tavily API but doesn't describe key behaviors such as rate limits, authentication needs, error handling, or what the search results include (e.g., headlines, summaries, sources). For a search tool with external API dependencies, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes the API name for context. Every word earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a search tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of articles with fields), how results are ordered, or any behavioral traits like pagination or API constraints. For a tool with rich input schema but missing output and behavioral context, it should do more.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples of how parameters interact or typical values). Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Search') and resource ('stock-related news'), and specifies the API used ('Tavily API'). It distinguishes from the sibling 'general-search' by focusing on stock-related content, though it doesn't explicitly mention this differentiation. The purpose is specific and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'general-search', nor does it mention any prerequisites, exclusions, or contextual triggers. It simply states what the tool does without indicating appropriate scenarios or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedgeneral-search
    • First observedsearch-stock-news
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

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'general-search' is for broad web searches, while 'search-stock-news' is specifically for stock-related news. There is no overlap or ambiguity between them, making it easy for an agent to select the appropriate tool based on the query context.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern with hyphens: 'general-search' and 'search-stock-news'. They use the same naming convention throughout, making the set predictable and readable without any deviations or mixed styles.

Tool Count2/5

With only two tools, the server feels under-scoped for a 'Search Stock News MCP Server'. While the tools cover general and stock-specific searches, the domain suggests potential for more operations like filtering, sorting, or retrieving detailed news, making the count too low for the apparent purpose.

Completeness2/5

The tool surface is significantly incomplete for a stock news server. It lacks essential operations such as filtering news by date, source, or stock ticker, retrieving trending news, or accessing detailed article content. This will likely cause agent failures when trying to perform comprehensive stock news analysis.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Tavily Search MCP Agent

    arben-adm
    A
    license
    Not graded
    quality
    D
    maintenance
    This MCP server performs multi-topic searches in business, news, finance, and politics using the Tavily API, providing high-quality sources and intelligent summaries.
    1
    MIT

  • Tavily News Search MCP Server

    binhtrongg
    -
    license
    Not graded
    quality
    Not graded
    maintenance
    A remote MCP server that enables searching for news articles on specific topics through the Tavily API without requiring authentication.
    -

  • gnews-mcp-server

    alejandro-ao
    F
    license
    Not graded
    quality
    F
    maintenance
    MCP server providing access to the GNews API for fetching news articles and headlines. Supports search and top headlines with advanced filtering by language, country, category, and date.
    1
    -

  • FinAgent

    gmoneyn
    A
    license
    A
    quality
    B
    maintenance
    Provides live stock data and market news for financial analysis via any MCP-compatible AI app.
    2
    MIT