Yfinance (yourusername) MCP Server
yfinance-mcp-server
PyPI
v1.0.4
Published by yourusername — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
A comprehensive yfinance MCP server providing access to Yahoo Finance data
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (test_mcp.py)MTC-SRC-002
In the server's implementation (`test_mcp.py:29`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: process proc = subprocess.Popen( [sys.executable, 'main.py'], stdout=subprocess.PIPE,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server test_mcp.py
Tools 23
Each tool and what it can reach — statically extracted from the published source.
configure_yfinanceno sensitive capabilityget_analyst_price_targetsno sensitive capabilityget_analyst_recommendationsno sensitive capabilityget_balance_sheetno sensitive capabilityget_cash_flowno sensitive capabilityget_dividends_and_splitsno sensitive capabilityget_earnings_calendarno sensitive capabilityget_earnings_estimatesno sensitive capabilityget_fast_infono sensitive capabilityget_fund_datano sensitive capability
Show 13 more tools ↓
get_income_statementno sensitive capabilityget_isinno sensitive capabilityget_multiple_stocks_historyno sensitive capabilityget_multiple_tickers_infono sensitive capabilityget_options_chainno sensitive capabilityget_ownership_datano sensitive capabilityget_sec_filingsno sensitive capabilityget_stock_historyno sensitive capabilityget_stock_infono sensitive capabilityget_stock_newsno sensitive capabilityget_sustainability_datano sensitive capabilityscreen_stocksno sensitive capabilitysearch_stocksno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.4 latest |
A 93/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan yfinance-mcp-server --online --registry pypiOther implementations of Yfinance 8
Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →
MCP server for Yahoo Finance data - stock quotes, historical prices, financials, company info, and news
unofficial Yahoo Finance API MCP Server - A Model Context Protocol server implementation for Yahoo Finance API
unofficial Yahoo Finance API MCP Server - A Model Context Protocol server implementation for Yahoo Finance API
MCP server providing comprehensive Yahoo Finance data access for AI assistants
MCP Server for Yahoo Finance API - AI-friendly financial data tools
A Model Context Protocol (MCP) server for agentic retrieval of financial market data. This server leverages YFinance to provide a simple and efficient way to access historical stock prices, dividends, stock splits, company information, and other financial metrics.
More in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.