yahoo-stock-mcp

English | 中文

Unofficial provider integrations / data-use notice

Yahoo Finance and Investing.com integrations in this project are unofficial. This project is not affiliated with, sponsored by, endorsed by, or authorized by Yahoo or Investing.com / Fusion Media.

Access to, storage of, and reuse or redistribution of upstream data may be restricted by provider terms and data licenses. Users are responsible for determining whether their use — including full-history sync, sync --all, local retention, and downstream use — complies with applicable terms, licenses, and law. This project grants no rights to upstream data.

Provider-access policy: transport compatibility may use ordinary protocol-level options such as standard TLS version selection, normal HTTP header casing, and a user-configured forward proxy. A bounded fallback across supported TLS profiles is allowed. The project must not implement CAPTCHA or JavaScript challenge solving, IP/account/identity rotation, credential spoofing, or unbounded retry behavior intended to defeat an explicit access denial. Recognized challenge/access-denial responses are surfaced as provider failures.

Provider terms can change. Review the current Yahoo Terms of Service and Investing.com Terms and Conditions for the jurisdiction and use case that apply to you.

An MCP server for stock-market data with unofficial Yahoo Finance and Investing.com integrations, backed by a local SQLite database.

What it does

• syncs quotes, fundamentals, ratios, dividends, earnings, holders, news, options, events, and sector data;

• stores normalized data in a local SQLite database and exposes it through MCP tools;

• computes 42 technical indicators locally from stored bars;

• uses Yahoo for daily/intraday bars and Yahoo + Investing for complementary fundamentals;

• supports scheduled live-provider contract checks;

• ships agent skills that turn those tools into repeatable research workflows.

Related MCP server: YFinance MCP Server

Documentation

• Usage — install, database setup, sync commands, MCP client config, environment variables, and proxy setup.

• Reference — MCP tools, tests, indicators, canonical metrics, and detailed data coverage.

• Skills — installable Agent Skills for company, sector, options, dividend, earnings, and technical research workflows, plus how to verify them.

• 中文使用说明 / 中文参考

Codex plugin

The repository also ships a portable Agent Plugin that bundles all seven skills with the MCP server configuration. Add this repository as a Codex marketplace source:

codex plugin marketplace add jamespud/yahoo-stock-mcp

Then install Yahoo Stock MCP from that marketplace in a supported Plugins Directory. The bundled stdio server runs the npm package version matching the plugin manifest. Node.js >= 22.13 and local YAHOO_STOCK_MCP_* configuration are required; the SQLite database is created automatically in a per-user data directory, and no external database service is needed. Credentials are never stored in the plugin files. For skill-only installation, see skills/README.md.

Data sources

• Yahoo Finance (unofficial): bars, quoteSummary, options, news, fundamentals-timeseries.

• Investing.com (unofficial): GraphQL quotes, financial statements, ratios, dividends, estimates, earnings, profile, executives, and holders.

• Bars are Yahoo-only. The former Investing TVC/K-line path has been removed.

Yahoo is the primary provider by default; Investing fills gaps. Set YAHOO_STOCK_MCP_PRIMARY_PROVIDER=investing to reverse the precedence.

Investing availability

The Investing integration uses a native Node transport with a bounded TLS compatibility profile and optional HTTP/HTTPS forward proxy support. It does not solve challenge pages. If supported profiles are rejected or Investing is otherwise unreachable, the provider failure is surfaced explicitly and a sync may report partial.

The scheduled live-provider canary hard-gates Yahoo and Investing data-contract/unit regressions. Investing network or access availability may report DEGRADED instead of failing the job because hosted-runner egress can be blocked independently of the provider contract. The canary is low-frequency and does not populate the project database or publish a data feed.

Upgrading from v0.4.0

v0.5.0 is a breaking release: MySQL support has been removed. SQLite is now the only backend, and there is no automatic data migration in this release.

If you have data in a MySQL database created by v0.4.x:

1. Back it up first. The database is untouched by the upgrade, but nothing in v0.5.0 will read it.

2. Re-sync into SQLite if you want to keep using this project. Be aware that a re-sync does not guarantee recovery of all history — some historical bars, news items and financial observations may no longer be available from the upstream providers.

3. To keep reading the old data, stay on v0.4.x. Old and new installs can coexist.

A one-off MySQL → SQLite migration tool is deferred and not part of v0.5.0. The historical v0.4.0 schema is preserved in the repository under scripts/mysql-to-sqlite/fixtures/ for that future work; it is not shipped in the npm package.

If any of YAHOO_STOCK_MCP_DATABASE_URL or YAHOO_STOCK_MCP_DB_* is still set, the server refuses to start and tells you so rather than silently creating an empty database.

Requirements

• Node.js >= 22.13

• No database service: a local SQLite file is created automatically on first use

• Provider access subject to the notices and upstream terms above

For setup and commands, continue with docs/USAGE.md.