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 クライアントと互換性があります。

Search Stock News MCPは、あらゆるMCPクライアントとシームレスに連携します。

モデル コンテキスト プロトコル (MCP) は、AI システムがさまざまなデータ ソースやツールとシームレスに対話し、安全な双方向接続を実現できるようにするオープン スタンダードです。

Search Stock News MCP サーバーは以下を提供します。

  • Tavily API によるリアルタイムの株価ニュース検索機能

  • 複数のカスタマイズ可能な検索クエリテンプレート

  • 設定可能な検索パラメータとフィルタリング

  • ドメイン固有のコンテンツフィルタリング

  • TypeScriptによる型安全な操作

前提条件🔧

始める前に、次のものを用意してください。

  • Tavily APIキー

  • Claude Desktop、Cursor、またはMCP互換クライアント

  • Node.js (v16 以上)

  • Git がインストールされている (Git インストール方法を使用する場合のみ必要)

Related MCP server: Tavily News Search MCP Server

株価ニュース検索MCPサーバーのインストール⚡

NPXで実行

npx -y search-stock-news-mcp@latest

Smithery経由でインストール

Smithery 経由で Claude Desktop 用の Search Stock News MCP Server を自動的にインストールするには:

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

MCP クライアントの設定 ⚙️

Cline の設定 🤖

Cline で Search Stock News MCP サーバーをセットアップする最も簡単な方法は、マーケットプレイスを使用することです。

  1. VS CodeでClineを開く

  2. サイドバーのClineアイコンをクリックします

  3. 「MCPサーバー」タブに移動します

  4. 「Search Stock News」を検索し、「インストール」をクリック

  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. Search Stock News サーバー構成を追加します。

{
  "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 デスクトップの設定 🖥️

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仕様のモデルコンテキストプロトコル

  • クロード・デスクトップのAnthropic

  • ニュース検索APIのTavily

ライセンス

マサチューセッツ工科大学

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