Financial Modeling Prep (FMP) MCP server providing access to financial data APIs including stock quotes, company profiles, historical data, financial statements, and market information
This server has significant definition quality issues. Of 26 tools, most have minimal descriptions and several are duplicated across files (search_symbol, company_profile, quote appear 2-3 times with varying quality). The server.mjs file uses Zod for input validation, which is better than server.js, but descriptions are still sparse and generic. Critical issues: tool duplication, inconsistent schema documentation, missing output schema documentation, and hardcoded API keys in source code (security risk). The best tools (in server.mjs) have 1-2 sentence descriptions; the worst (in index.js, which appears incomplete) have only minimal names. No tools declare output schemas. Error handling is basic (try/catch with generic 'Error' messages). Naming follows verb_noun convention reasonably well, but many parameter descriptions are vague (e.g., 'Period (annual or quarter)' does not explain WHY this parameter matters or when to use one vs. the other).
Get balance sheet for a stock
Get cash flow statement for a stock
Get company profile by symbol
Get a curated summary of the company profile by symbol.
Get crypto tickers
Get DCF valuation for a stock
Get upcoming earnings announcements
Tool duplication across files: search_symbol, company_profile, and quote are defined 2-3 times in server.js, server.mjs, and index.js with inconsistent schemas and descriptions. This creates confusion about which version is the canonical one.
Hardcoded API key in server.js: line 'const API_KEY = process.env.FMP_API_KEY || "e8ae18df38837f283f9bb1684f21788f"' exposes a live API key in source code. This is a critical security vulnerability.
No output schemas documented: None of the 26 tools document what fields are returned or their types. LLMs cannot plan downstream tool calls or extract needed data without knowing the response structure.
Generic and minimal descriptions: 16 tools have descriptions under 60 characters (e.g., 'Get ETF tickers', 'Get forex tickers', 'Get crypto tickers'). These provide no context for when to use the tool or what it returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Get enterprise value and related metrics for a stock
Get ETF holdings by symbol
Get ETF tickers
Get financial ratios for a stock
Get forex tickers
Get historical price data for a stock
Get historical stock data (daily or intraday) for a symbol. Supports summary or more detailed output.
Get income statement for a stock
Get insider trading activity for a stock
Get upcoming IPOs
Get key financial metrics for a stock
Get mutual fund holdings by symbol
Get mutual fund tickers
Get a concise real-time quote for a stock.
Get real-time quote for a stock
Search for a stock symbol by company name or symbol
Search for a stock symbol by company name or symbol. Returns top matches.
Get latest news for a stock
Screen stocks by market cap, sector, price, etc.
Parameter descriptions lack actionable detail: Many parameters like 'period' are described only as enum values without explaining their purpose or consequences. E.g., 'Period (annual or quarter)' does not explain when annual vs quarterly data should be used or what the differences are.
Inconsistent parameter documentation: server.js tools lack detailed parameter descriptions compared to server.mjs tools. For example, search_symbol in server.mjs has 'limit' with a description of 'Number of results to fetch from API. Defaults to 10. A smaller summary will be returned.' but server.js version has no limit parameter documented.
No error recovery guidance: All error handling returns generic messages like 'Error in search_symbol: <error.message>'. LLMs have no guidance on whether to retry, which parameters to adjust, or what to do next.
Optional parameters lack clear defaults: Parameters like 'limit' in stock_screener and earnings_calendar have no stated defaults or ranges. Unbounded numeric params let LLMs pass absurd values.
No tool annotations: None of the tools declare readOnlyHint, destructiveHint, or idempotentHint in the current MCP spec (2026-07-28). All tools are read-only (financial data), so readOnlyHint=true should be declared for every tool.
Vague parameter names and types: Parameters like 'from' and 'to' in earnings_calendar lack type hints (should be 'string' with ISO 8601 format). Parameter 'exchange' in stock_screener is undocumented (no enum of valid exchanges, no description of format).