@qubaomingg/stock-mcp
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 (get one for free at Alpha Vantage) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-stock-dataD | – |
| get-stock-alertsD | – |
| get-daily-stock-dataD | – |
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 3 tools
The tools are highly ambiguous and overlapping. 'get-daily-stock-data' and 'get-stock-data' appear to serve nearly identical purposes, with no description to clarify their differences. 'get-stock-alerts' might be distinct but lacks context, making the overall set confusing and prone to misselection.
The naming is perfectly consistent, using a kebab-case pattern with a 'get-' prefix followed by a noun phrase. All three tools follow this exact convention, making them predictable and easy to parse.
With only 3 tools, the set feels thin and under-scoped for a stock data server. It lacks essential operations like search, update, or delete, and the limited coverage suggests it may not support comprehensive agent workflows in this domain.
The tool surface is severely incomplete for a stock data domain. It only provides 'get' operations with no ability to set, modify, or manage data (e.g., no create, update, delete, or search tools). This will cause significant agent failures in handling stock-related tasks.