Financial Data MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALPHA_VANTAGE_API_KEY | Yes | Your Alpha Vantage API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getStockQuoteA | Get the current quote for a stock. |
| getHistoricalDataC | Get historical data for a stock. |
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
The two tools, getStockQuote and getHistoricalData, are clearly distinct: one provides current real-time data while the other provides historical time-series data. There is no overlap or ambiguity in their purposes.
Both tool names follow the same pattern: 'get' plus a descriptive noun in camelCase. This is consistent and predictable, making it easy for an agent to infer the action and resource.
With only two tools, the server feels thin for a financial data service. While the two tools cover basic stock quote and historical data needs, the count is at the lower boundary of what is considered reasonable for a domain-focused server.
The server covers fundamental stock data retrieval (current and historical), but lacks other common financial data operations such as company fundamentals, options chains, or market indices. The surface is functional but minimal.