F
licenseNot graded
qualityD
maintenanceEnables querying Yahoo Finance data including stock prices, historical data, financial statements, dividends, news, analyst recommendations, and company information through the yfinance library.
FinanceExpert
by geddamsatish
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FinanceExpertWhat's the current stock price and trend for AAPL?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-stock-server (FinanceExpert)
A small Model Context Protocol server built with FastMCP. It exposes Yahoo Finance market data (via yfinance) so assistants can fetch quotes, history as CSV, and plain-text Unicode price charts.
Requirements
Python 3.11+
uv (recommended) or another way to install dependencies from
pyproject.toml
Related MCP server: Yahoo Finance MCP Server
Setup
cd mcp-stock-server
uv syncRun (stdio)
The server speaks MCP over stdio (the default for mcp.run()):
uv run python server.pyAdd as an MCP server (Cursor)
Open Cursor Settings → MCP (or edit your MCP JSON config — often
~/.cursor/mcp.jsonon macOS/Linux).Register a stdio server whose working directory is this repo and whose command starts
server.py.
Option A — uv run (recommended)
Replace /absolute/path/to/mcp-stock-server with the real path where you cloned the repo.
{
"mcpServers": {
"FinanceExpert": {
"command": "uv",
"args": ["run", "python", "server.py"],
"cwd": "/absolute/path/to/mcp-stock-server"
}
}
}After uv sync, this uses the locked dependencies from uv.lock.
Option B — project virtualenv Python
Use this if you prefer not to invoke uv from the MCP client:
{
"mcpServers": {
"FinanceExpert": {
"command": "/absolute/path/to/mcp-stock-server/.venv/bin/python",
"args": ["server.py"],
"cwd": "/absolute/path/to/mcp-stock-server"
}
}
}Create the venv first (from the repo root): uv sync (installs deps into .venv).
Save the config and restart Cursor (or reload MCP). In the MCP panel you should see FinanceExpert with tools
get_stock_analysis,get_historical_prices, andget_stock_price_chart.
Other MCP clients (e.g. Claude Code, editors with MCP support) use the same idea: command + args + cwd for a stdio server.
Tools
Tool | Description |
| Snapshot text: current price, 50-day average, analyst recommendation key (from |
| Daily close column as CSV for a lookback of |
| Box-drawn ASCII/Unicode chart: area fill, price axis, start/end dates on the time axis, and an 8-step sparkline. |
get_stock_price_chart parameters
ticker— Symbol, e.g.INTU,AAPL.days— Used whenperiodis omitted: Yahoo rangeNd(calendar days). Default 30.period— Optional Yahoo period string; when set, it overridesdays. Examples:10y,5y,1y,6mo,ytd,max.
Examples:
Last month of sessions (by calendar days):
days=30Last ten calendar years (Yahoo window):
period="10y"
Market data comes from Yahoo through yfinance; semantics match yfinance history(period=...).
Disclaimer
Quotes and history are informational only, not investment advice. Yahoo data can lag or contain errors; verify independently for decisions.
Available Tools
3 toolsget_historical_pricesC
Fetches historical closing prices for chart generation.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes | ||
| days | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
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 description must disclose behavioral traits. It does not mention whether data is cached, any limits on 'days' parameter, or output format beyond 'closing prices'. No contradiction with annotations.
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?
Description is one concise sentence, front-loaded with purpose. No fluff, but could be longer for completeness.
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 an output schema exists, return values are covered. However, no guidance on parameter ranges or timezone for days, and no usage context for how this relates to chart generation. Incomplete for a tool with zero annotations.
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 0%, so description should compensate. It adds no detail about 'ticker' or 'days' beyond their names. Baseline is 3 due to absence of param info in description.
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 tool fetches historical closing prices for chart generation, specifying the action (fetch), resource (historical prices), and purpose (chart generation). However, it does not differentiate from sibling tools like get_stock_price_chart or get_stock_analysis.
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 siblings. It does not mention prerequisites, alternatives, or contexts where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_stock_analysisA
Fetches real-time stock price, 50-day average, and analyst recommendations.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
A3.5/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It indicates the tool fetches data (non-destructive), but does not disclose any potential latency, rate limits, or data freshness. The output schema exists but is not referenced; description could hint at what fields are returned beyond what's in schema.
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 concise at one sentence, front-loading the key output fields. Every phrase adds value, with no waste.
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 tool has one simple parameter and an output schema, the description could be more complete by adding a note about the ticker format or data source. It is adequate but lacks some contextual details like time zone or data provider.
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 0% (no description for the parameter), so the description must compensate. It does not explain what the ticker parameter expects (e.g., format, examples). However, the parameter has no enums and is simple, so the gap is small. Baseline 3 is appropriate.
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 it fetches real-time stock price, 50-day average, and analyst recommendations. The verb 'fetches' and the specific resources are well-defined, but it does not distinguish itself from sibling tools like get_historical_prices or get_stock_price_chart.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for obtaining current price, average, and recommendations, but provides no explicit guidance on when to use this tool versus alternatives. For instance, it does not mention that get_historical_prices might be for historical data or get_stock_price_chart for chart data.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_stock_price_chartA
Plain-text Unicode chart. Pass period (e.g. 10y, 5y, 1y) for calendar ranges, or use days alone.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | Yes | ||
| days | No | ||
| period | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the output format (plain-text Unicode chart) and the two ways to specify time range, but does not mention rate limits, data latency, or whether it requires authentication. The behavior is partially transparent.
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 two sentences, no waste. It front-loads the key purpose and follows with parameter guidance. Efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema, the description does not need to detail return structure. It covers the main purpose, parameter usage, and output format. For a simple chart tool with 3 parameters, this is reasonably complete.
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 0%, so the description must compensate. It explains 'period' and 'days' parameters by specifying their relationship (period for calendar ranges, days alone). However, it does not describe the 'ticker' parameter or the exact format of 'period'. This adds some meaning but not comprehensive.
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 specifies a verb-resource-action: it creates a plain-text Unicode chart for a stock. It is distinct from 'get_historical_prices' and 'get_stock_analysis' as it focuses on chart output, though it does not explicitly differentiate from those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear guidance on how to specify the time range: use period for calendar ranges or days alone. However, it does not explain when to prefer this tool over its siblings (e.g., when you need a visual chart vs. raw prices or analysis).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
TDQS
A3.5/5.0
Disambiguation4/5
Tools are mostly distinct: get_historical_prices provides raw data for charts, get_stock_analysis gives real-time price and fundamentals, and get_stock_price_chart returns a visual chart. However, get_historical_prices and get_stock_price_chart both relate to historical data, causing slight overlap.
Naming Consistency5/5
All tools use a consistent get_verb_noun pattern (get_historical_prices, get_stock_analysis, get_stock_price_chart). Naming is clear and predictable.
Tool Count5/5
With 3 tools covering historical data, real-time analysis, and charting, the set is appropriately scoped for a finance assistant. No tool feels unnecessary.
Completeness3/5
The tools cover basic stock data retrieval and charting but lack fundamental operations like search, comparison, or portfolio management. Gaps exist for a fully comprehensive finance tool.
Maintenance
ActivityInactive
ResponsivenessNo issues
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Scrape stock quotes, historical prices, and financial statements from Yahoo Finance.
Fetch current stock prices and key data for symbols across global markets. Look up companies like…
Real-time stock quotes and technical signals: RSI, MACD, SMA crossovers via Yahoo Finance.
Portfolio-aware finance tools: drift, risk, earnings, benchmarks, news, tax harvesting
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to retrieve stock market data and financial information from Yahoo Finance using the yfinance Python library. Supports querying stock prices, historical data, and other financial metrics through natural language.MIT
- AlicenseAqualityDmaintenanceEnables retrieval of comprehensive financial data from Yahoo Finance, including stock prices, company info, financial statements, options, and news, for stock analysis and market research.9344MIT
- AlicenseAqualityCmaintenanceProvides access to Yahoo Finance data including real-time stock quotes, historical prices, financial statements, company info, symbol search, and news.6451MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/geddamsatish/mcp-stock-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server