yfinance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_priceC | Get the price of a stock/crypto ticker. |
| get_newsC | Get the news of a stock/crypto ticker. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
get_news and get_price target distinct aspects (news vs. price) with no overlap. An agent can easily choose the correct tool for the intended action.
Both tools follow the consistent pattern of get_<resource>, using snake_case and a clear verb-noun structure. No deviations.
With only 2 tools for a domain as rich as stock/crypto data, the set is far too sparse. Most financial APIs offer dozens of endpoints; this limited set feels incomplete.
Crucial operations are missing: no historical price data, no financial statements, no market statistics, no search. An agent cannot perform basic financial analysis with just news and current price.