F
licenseNot graded
qualityD
maintenanceProvides real-time stock market data through Yahoo Finance without requiring an API key. Get quotes, historical data, company information, financial statements, and ticker search capabilities.
-
Finance MCP Server
by ryar001
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., "@Finance MCP ServerGet the income statement for Apple"
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.
Finance MCP Server
A Model Context Protocol (MCP) server that provides financial data for LLMs. This server specifically fetches financial statements (Income Statement, Balance Sheet, Cash Flow) for public companies.
Features
Free to use: No API keys required.
Structured Data: Returns data in consistent Pydantic models (JSON schema).
Easy Integration: Works with any MCP-compliant client (Claude Desktop, Cursor, etc.).
Related MCP server: Financial Datasets MCP Server
Data Source
This package retrieves financial data from Yahoo Finance using the yfinance library.
Note: This tool is for educational and research purposes. Please respect Yahoo Finance's terms of service.
Installation & Usage
Option 1: Quick Use with uvx (Recommended)
You can run this server directly without standard installation using uv (or uvx).
Add this to your MCP settings configuration (e.g., ~/.config/Claude/claude_desktop_config.json or your IDE's MCP config):
{
"mcpServers": {
"finance": {
"command": "uvx",
"args": [
"finance-mcp-free"
]
}
}
}Option 2: Local Development (Git Clone)
If you want to modify the code or run it locally:
Clone the repository:
git clone https://github.com/ryar001/finance_mcp.git cd finance_mcpInstall dependencies:
# Using uv (recommended) uv venv source .venv/bin/activate uv sync # Or using pip pip install -e .Run the server:
# Run directly finance-mcp # Or via fastmcp dev for auto-reload fastmcp dev finance_mcp/main_mcp.py:mcp_server
Data Models
The server returns data structured according to strict Pydantic models to ensure reliability for your LLM.
Example Return Format
All financial statements return a dictionary where keys are dates and values are the statement object.
Income Statement Example:
{
"30/09/2023": {
"ticker": "AAPL",
"period": "30/09/2023",
"total_revenue": 89498000000,
"net_income": 22956000000,
"cost_of_revenue": 49071000000,
"gross_profit": 40427000000,
"operating_expenses": 13458000000,
"operating_income": 26969000000,
...
}
}The data is strictly typed to ensure your LLM can reliably query fields like total_revenue, net_income, etc.
Available Tools
3 toolsget_balance_sheet_toolA
Retrieve the balance sheet for a specified company.
company: The name of the company for which to retrieve the balance sheet.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
A3.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states the action. It fails to disclose behavioral traits such as data freshness, rate limits, or authentication requirements. While the operation is read-only by implication, the description does not explicitly confirm this.
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: one sentence plus a single parameter bullet. No filler, front-loaded with the core action.
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 presence of an output schema, return values are covered. However, the description lacks guidance on when to choose this tool over siblings and does not address prerequisites or data scope. Adequate for a simple tool but leaves gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds a clear explanation for the sole parameter 'company' (the name of the company), which is absent from the schema (coverage 0%). This adds significant value, though it could be more specific (e.g., ticker vs. full name).
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 it retrieves the balance sheet for a specified company, matching the tool name and distinguishing it from sibling tools (cash flow, income statements).
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?
No explicit guidance on when to use or avoid this tool, nor any differentiation from siblings. Usage is implied from the tool name, but no alternatives or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_cashflow_statement_toolB
Retrieve the cash flow statement for a specified company.
company: The name of the company for which to retrieve the cash flow statement.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
B3.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It does not mention any side effects, access requirements, rate limits, or output format, which is a critical gap.
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 consists of two short sentences: one for the tool's purpose and one for the parameter. It is front-loaded and efficient, with no wasted words.
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's simplicity (one parameter, no nested objects) and the presence of an output schema, the description provides the bare minimum. It adequately identifies the resource and parameter but lacks usage and behavioral context.
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?
With 0% schema description coverage, the description adds meaning to the 'company' parameter by stating it is the company name for the statement. However, it lacks specificity (e.g., full name vs. ticker) and does not compensate for the missing schema descriptions.
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 retrieves the cash flow statement for a specified company, using a specific verb and resource. The resource name distinguishes it from sibling tools (balance sheet and income statement), making its purpose unambiguous.
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. There is no mention of appropriate contexts, prerequisites, or exclusions, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_income_statement_toolC
Retrieve the income statement for a specified company.
company: The name of the company for which to retrieve the income statement.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must convey behavioral traits. It only states 'retrieve', implying read-only, but does not disclose data freshness, scope, or any side effects. This is insufficient for a tool with no annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short, consisting of one sentence and a parameter bullet. While concise, it lacks clear structure and separates the parameter description as a sub-bullet, which is acceptable but not exemplary.
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 that an output schema exists, the description need not detail return values. However, it omits context such as time period (e.g., quarterly vs annual) and currency, which are typical for income statements. The description is minimally complete for a simple tool but could be more informative.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, so the description must compensate. It describes the 'company' parameter as 'The name of the company', but does not specify acceptable formats (e.g., ticker, full name) or provide examples. This adds minimal meaning beyond the schema.
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 retrieves an income statement for a specified company, using the specific verb 'retrieve' and resource 'income statement'. However, it does not differentiate from sibling tools like get_balance_sheet_tool or get_cashflow_statement_tool, which are also financial statements.
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?
No guidance is provided on when to use this tool versus the siblings. There is no mention of prerequisites, such as company identifier format, or any exclusions.
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. Dates show when Glama detected each change.
3 tool updates
v0.1.4- First observed
get_balance_sheet_tool - First observed
get_cashflow_statement_tool - First observed
get_income_statement_tool
TDQS
B3.4/5.0
Disambiguation5/5
Each tool retrieves a distinct financial statement (balance sheet, cash flow, income statement) with no overlap in functionality.
Naming Consistency5/5
All tool names follow the 'get_{statement_type}_tool' pattern, using consistent verb-noun structure despite the redundant '_tool' suffix.
Tool Count4/5
Three tools is a reasonable minimal set for a finance server focused on core financial statements, though additional tools (e.g., financial ratios) could be included.
Completeness4/5
The three primary financial statements are covered, which is complete for basic financial data retrieval; missing features like historical comparisons or sector data are minor gaps.
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.
Income statement, balance sheet and cash flow, already assembled from SEC filings. No API key.
Financial statements, metrics, dividends, and price data for public companies.
- mcpOAuthsh.opencapital
Give your AI deep fundamentals on US public companies — metrics, segments, peers. Free.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides access to comprehensive financial data including income statements, balance sheets, cash flow statements, stock prices, company news, SEC filings, and cryptocurrency information with built-in financial ratio analysis.-
- FlicenseNot gradedqualityDmaintenanceEnables querying Yahoo Finance data including stock prices, historical data, financial statements, dividends, news, analyst recommendations, and company information through the yfinance library.-
- AlicenseNot gradedqualityDmaintenanceProvides 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
Appeared in Searches
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/ryar001/finance_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server