MCP server for Alpha Vantage stock market data providing intraday and daily stock prices, volumes, and price movement alerts
Three tools are registered with Zod schemas and descriptions visible in src/index.ts. Tool naming follows verb-noun convention (get_*), which is appropriate. All tools have non-empty descriptions (103-159 chars) and documented parameters. However, there are significant gaps: (1) output schemas are completely undocumented, responses are returned as plain text wrapped in {type: 'text', text: data} without specifying what data structure the underlying API returns or how it should be interpreted; (2) error handling is minimal, errors are caught but returned as generic text without recovery guidance or error classification; (3) parameter descriptions lack constraint details (e.g., no guidance on valid stock symbol formats, no mention of Alpha Vantage rate limits or response time expectations); (4) no tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only; (5) resource implementation (stock://{symbol}/{interval}) is present but underdocumented and not integrated with tool output schemas. The server is functional for basic stock data retrieval but lacks production-grade documentation and error guidance.
Fetches daily stock data from Alpha Vantage API for a given stock symbol
Analyzes stock data to generate alerts based on price movements exceeding a specified threshold percentage
Fetches stock data from Alpha Vantage API for a given symbol and time interval
Output schemas completely undocumented. All three tools return {content: [{type: 'text', text: data}]} but 'data' is raw API response text with no documented field structure, format, or meaning. LLMs cannot plan downstream calls or extract structured data.
Error handling lacks recovery guidance. Errors are caught and returned as plain text (e.g., 'Error fetching stock data: ...') without categorization (retryable vs. user-fixable vs. fatal) or next-step suggestions. LLMs cannot determine whether to retry, ask the user, or abort.
Parameter descriptions lack constraint details. 'symbol' parameter has no guidance on valid formats (e.g., 'US stock symbols are 1-5 uppercase letters'). 'threshold' has no range specification (0-100%? unbounded?). 'interval' enum is documented but no explanation of which intervals are available for intraday vs. daily data. 'outputsize' enum is documented but no guidance on when to use compact vs. full (compact limit, full limit).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 54 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 43 | - | v1 |
Missing tool annotations despite all tools being read-only. Tools should declare readOnlyHint=true so agents know these calls are safe to retry and have no side effects. This is a low-cost, high-value addition.
Resource implementation (stock://{symbol}/{interval}) exists but is underdocumented. No description of when to use it vs. tools, no guidance on available intervals, and response format is identical to tools (plain text). Resources should provide either different/richer data or be removed to reduce cognitive load.
No mention of Alpha Vantage API rate limits, rate limit exceeded behavior, or timeout guidance. The alphaVantage.ts module calls axios.get() without explicit timeout configuration. If the API is slow or rate-limited, agents may hang indefinitely. No guidance on how to handle 'Note' responses (API usage alerts).