FinDataMCP
FinDataMCP
Для запуска:
Клонировать репозиторий
Установить uv (менеджер пакетов):
curl -LsSf https://astral.sh/uv/install.sh | shПерейдите в папку:
cd FinDataMCPУстановите зависимости:
# Create virtual env and activate it uv venv source .venv/bin/activate # Install dependencies uv add "mcp[cli]" httpx yfinanceПроверьте, что все работает, запустив сервер:
uv run findata.py
Related MCP server: mysqldb-mcp-server
Подключение к Claude Desktop
Установите Claude Desktop, если вы еще этого не сделали.
Редактировать файл конфигурации Claude Desktop (Claude>Настройки>Разработчик>Изменить конфигурацию):
Добавьте следующую конфигурацию:
{ "mcpServers": { "findata": { "command": "uv", "args": [ "--directory", "/ABSOLUTE/PATH/TO/PARENT/FOLDER/FinDataMCP", "run", "findata.py" ] } } }Перезагрузить рабочий стол Клода
Для команд Windows: см. https://modelcontextprotocol.io/quickstart/server
Available Tools
1 toolget_stock_priceB
Get the current stock price using yfinance.
Args:
symbol: Stock ticker (e.g. AAPL, TSLA, MSFT)
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the data source (yfinance) but lacks critical behavioral details such as rate limits, error handling, freshness of data, or authentication requirements for a financial data tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized and front-loaded with the core purpose, followed by parameter details. It avoids unnecessary fluff, though the formatting with 'Args:' could be slightly more polished.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and a single parameter, the description is incomplete. It lacks information on return values, error cases, and operational constraints, which are essential for effective tool use in an AI agent context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description compensates by explaining the 'symbol' parameter as 'Stock ticker' with examples (AAPL, TSLA, MSFT), adding meaningful context beyond the bare schema. However, it doesn't cover all potential nuances like format constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Get') and resource ('current stock price'), and mentions the data source ('using yfinance'). However, since there are no sibling tools, it cannot demonstrate differentiation from alternatives, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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, prerequisites, or limitations. It only states what the tool does without context for usage decisions.
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.
1 tool update
v1.0.0- First observed
get_stock_price
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on retrieving stock prices.
The single tool name follows a clear verb_noun pattern (get_stock_price). With only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for a server named 'FinDataMCP', which suggests a broader financial data domain. This minimal toolset severely limits functionality and does not align with the implied scope of financial data operations.
The tool surface is severely incomplete for a financial data server. It only provides stock price retrieval, missing essential operations like historical data, financial statements, market indices, currency rates, or any other common financial data queries.
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
MCP server giving AI agents one-connection access to China A-share market intelligence: financials,
MCP server giving Claude AI access to 22+ NYC public-record databases for real estate due diligence
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
The Octagon MCP server provides specialized AI-powered financial research and analysis by integrating with the Octagon Market Intelligence API. It enables users to analyze public market data (SEC filings, earnings transcripts, financial metrics, and stock data for 8000+ companies), private market data (3M+ companies, 500k+ funding rounds, 2M+ M&A/IPO transactions), and conduct deep research including web scraping capabilities. The server also features autonomous research agents that search hundreds of sources and return fully cited reports in approximately one minute.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that allows accessing and managing ledger files through Claude by providing account listing, balance checking, and transaction register viewing capabilities.4GPL 3.0
- AlicenseCqualityDmaintenanceAn MCP server that enables MySQL database integration with Claude. You can execute SQL queries and manage database connections.29MIT
- AlicenseAqualityAmaintenanceA simple MCP server for Yahoo Finance using yfinance. This server provides a set of tools to fetch stock data, news, and other financial information.15189MIT
- AlicenseBqualityDmaintenanceAn MCP server that provides comprehensive financial insights and analysis by leveraging real-time market data, news, and advanced analytics for stocks, options, financial statements, and economic indicators.1751PythonMIT
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/coreyjwang/FinDataMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server