Skip to main content
Glama
mokemokechicken

yfinance-mcp-server

yfinance-mcp-server

日本語版

Important Note: This is an unofficial MCP server.

A Model Context Protocol (MCP) server for accessing Yahoo Finance data with comprehensive technical analysis features. This server provides AI-friendly structured stock analysis through Yahoo Finance API.

This project is based on onori/yfinance-mcp-server and has been enhanced with comprehensive technical analysis features.

Features

  • Comprehensive Stock Analysis: Get detailed financial metrics, technical indicators, and AI-friendly Japanese reports

  • Technical Indicators: RSI, MACD, Bollinger Bands, Stochastic, Moving Averages, VWAP, Volume Analysis

  • Financial Metrics: Market cap, P/E ratio, P/B ratio, ROE, EPS growth, dividend yield

  • Multi-Market Support: US stocks (AAPL), Japanese stocks (7203.T), crypto (BTC-USD), forex (EURUSD=X)

  • AI-Optimized Output: Structured Japanese reports with emojis for better AI understanding

  • Performance Optimized: Maximum 2 API calls with comprehensive local calculations

Related MCP server: Stockflow MCP Server

Installation

Claude Code MCP Configuration

Use the Claude Code CLI to add the MCP server:

claude mcp add yfinance npx @mokemokechicken/yfinance-mcp-server

Or manually add to your Claude Code MCP settings:

{
  "mcpServers": {
    "yfinance": {
      "command": "npx",
      "args": ["@mokemokechicken/yfinance-mcp-server"]
    }
  }
}

Other MCP Clients (Cursor, etc.)

{
  "mcpServers": {
    "yfinance": {
      "command": "npx",
      "args": ["@mokemokechicken/yfinance-mcp-server"]
    }
  }
}

Local CLI

MCP を介さずにローカルで分析する場合は CLI を使えます。

npm run cli -- AAPL
npm run cli -- 6301.T --days 5
npm run cli -- AAPL --technical-params '{"rsi":{"overbought":80}}'
npm run cli -- AAPL --json

ビルド後は yfinance-analyze コマンドとしても使えます。

Available Tool

getStockAnalysis

Performs comprehensive stock analysis with technical indicators and financial metrics.

Parameters:

  • symbol (required): Stock symbol

    • US stocks: AAPL, GOOGL, MSFT

    • Japanese stocks: 7203.T, 6301.T, 9984.T

    • Crypto: BTC-USD, ETH-USD

    • Forex: EURUSD=X, USDJPY=X

  • days (optional): Number of days for recent price data display (default: 7, range: 1-365)

Example Usage:

> Please analyze Apple stock (AAPL) for the last 5 days

> Analyze Toyota Motors (7203.T) with default 7-day period

Response includes:

  • 📊 Recent stock price data

  • 💰 Financial metrics (market cap, P/E, ROE, etc.)

  • 📈 Technical indicators (RSI, MACD, Bollinger Bands, etc.)

  • 🎯 Trading signals and trend analysis

  • 📋 AI-friendly structured Japanese report

Development

To set up the development environment:

  1. Clone the repository

  2. Install dependencies:

npm install
  1. Start the development server:

npm run dev

License

ISC License (ISC)

Available Tools

1 tool
getStockAnalysisB

包括的な株式分析を実行し、財務指標、テクニカル指標、統合シグナル分析を含む投資分析レポートを提供します。技術指標パラメータのカスタマイズが可能です。(v1.3.1)

ParametersJSON Schema
NameRequiredDescriptionDefault
symbolYes株式銘柄コード(例:米国株=AAPL、日本株=7203.T、仮想通貨=BTC-USD、為替=EURUSD=X)
daysNo直近何日分の価格推移データを返すか(デフォルト:7日)
technicalParamsNo技術指標パラメータ設定(オプション)。指定しない場合はデフォルト値を使用

TDQS

B3.2/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. It does not disclose whether the tool is read-only, has side effects, or requires authentication. The description implies analysis but lacks explicit behavioral context.

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

Conciseness4/5

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

The description is a single sentence with a version note, making it very concise. It front-loads the core action, though it could be slightly more detailed without harming conciseness.

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

Completeness3/5

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

Given the complexity (nested parameters, no output schema), the description is adequate but incomplete. It lists components but does not explain output format or behavior for edge cases, leaving some gaps.

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 baseline is 3. The description adds only a generic mention of customizable technical parameters, which does not significantly enhance understanding beyond the schema.

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

Purpose5/5

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

The description clearly states the tool performs comprehensive stock analysis including financial indicators, technical indicators, and integrated signal analysis. It also mentions customization of technical parameters, which uniquely identifies its purpose.

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, nor does it mention any prerequisites or exclusions. It simply describes the tool's function.

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. 1 tool updatev1.3.1
    • First observedgetStockAnalysis

TDQS

B3.4/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is clearly defined.

Naming Consistency5/5

With only one tool, naming is trivially consistent. The name 'getStockAnalysis' follows a clear verb_noun pattern.

Tool Count2/5

A single tool for a financial data server like yfinance is too few. Typically, multiple tools for quotes, financials, history, etc., are expected, making this feel under-scoped.

Completeness3/5

The one tool claims to provide comprehensive stock analysis, but it likely misses other common yfinance features like historical data or news, leaving notable gaps for agents.

Maintenance

ActivityInactive
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides comprehensive financial data from Yahoo Finance, enabling retrieval of stock prices, company information, financial statements, options data, analyst recommendations, and market news through natural language queries.
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Provides comprehensive financial data and analysis tools using Yahoo Finance, including real-time stock data, historical data with technical indicators, options chains, and financial statements.
    3
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides TradingView-style market analysis with OHLCV candles, 19 technical indicators, a screener, and a backtester using public Yahoo Finance data without API keys.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables assistants to retrieve Yahoo Finance data for Japanese and US equities, including quotes, financial statements, key ratios, historical prices, and analyst recommendations.
    MIT