Yahoo Finance MCP Server
Related Servers
Alternatives to Yahoo Finance MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes real-time financial data tools for stock search, company info, historical prices, and financial metrics from Yahoo Finance, enabling AI agents to answer natural-language questions about stocks and financial markets.MIT
- AlicenseAqualityDmaintenanceEnables querying stock data, financial information, news, and historical prices from Yahoo Finance through a set of MCP tools.5MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server that provides comprehensive access to Yahoo Finance data through 18 specialized tools for pricing, financials, options, holders, and news.1829 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, ChatGPT, and Notion to retrieve Yahoo Finance quotes, price history, fundamentals, analyst and holder data, options, funds, screeners, market summaries, calendars, and live ticks through 24 tools. It supports remote Streamable HTTP access with OAuth 2.1, Basic auth, and client credentials.MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that provides seamless access to Yahoo Finance stock market data, enabling retrieval of real-time quotes, historical data, charts, financial summaries, and market searches.25 npmISC
- FlicenseNot gradedqualityCmaintenanceMCP server wrapping yfinance to provide stock market data, financials, and analytics via 24 tools.-
TDQS
Scored across 24 tools
Most tools map to clearly distinct Yahoo endpoints (quote, history, financials, holders, options, screen, sector), and the descriptions actively disambiguate the tricky pairs like get_quote vs get_quotes and get_fund_data vs get_company_info. However, get_earnings, get_calendar, and get_estimates overlap around earnings dates and analyst estimates, and get_sector/get_industry could be confused with symbol-based lookups despite the warnings.
A strong, predictable get_<resource> pattern covers the large majority of the 24 tools, all in snake_case with no camelCase mixing. The deviations are a few non-get verbs (search, screen, server_status) that are still readable but break the otherwise uniform convention.
24 tools is on the heavy side of the ideal band, but each corresponds to a genuinely different slice of Yahoo Finance data (fundamentals, ownership, analyst, options, screening, discovery), so none feels redundant. The only mild padding is the overlap between get_earnings, get_calendar, and get_estimates.
The surface spans the full lifecycle: symbol discovery, quotes, history, statements, dividends/splits, ownership, insider activity, analyst coverage, options, SEC filings, fund data, screening, and sector/industry/market browsing. There are no obvious dead ends for a finance data agent, and known upstream limitations (non-US options, non-US SEC filings) are explicitly documented.