mcp-finnhub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FINNHUB_API_KEY | Yes | Your Finnhub API key (required). | |
| FINNHUB_STORAGE_DIR | Yes | Path to the storage directory for project data (required). | |
| FINNHUB_RATE_LIMIT_RPM | No | Requests per minute limit (optional). | 300 |
| FINNHUB_REQUEST_TIMEOUT | No | Request timeout in seconds (optional). | 30 |
| FINNHUB_SAFE_TOKEN_LIMIT | No | Conservative token limit (optional). | 75000 |
| FINNHUB_ENABLE_NEWS_SENTIMENT | No | Enable news sentiment tools (optional). | true |
| FINNHUB_ENABLE_STOCK_MARKET_DATA | No | Enable stock market data tools (optional). | true |
| FINNHUB_ENABLE_TECHNICAL_ANALYSIS | No | Enable technical analysis tools (optional). | true |
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 |
|---|---|
| finnhub_stock_market_dataC | Real-time quotes, historical candles, and company profiles. Operations:
|
| finnhub_news_sentimentC | Company news, market news, and sentiment analysis. Operations:
|
| finnhub_technical_analysisC | Technical indicators, patterns, and signals. Operations:
|
| finnhub_stock_fundamentalsA | Financial statements, earnings, dividends, and splits. Operations:
For get_basic_financials:
|
| finnhub_stock_estimatesA | Analyst estimates for earnings, revenue, EBITDA, and price targets. Operations:
|
| finnhub_stock_ownershipB | Insider trades, institutional ownership, and congressional trading. Operations:
|
| finnhub_alternative_dataC | ESG scores, social sentiment, supply chain, and patents. Operations:
|
| finnhub_sec_filingsC | SEC filings, filing sentiment, and similarity analysis. Operations:
|
| finnhub_crypto_dataC | Cryptocurrency exchanges, symbols, profiles, and candles. Operations:
|
| finnhub_forex_dataB | Foreign exchange rates, symbols, and candles. Operations:
|
| finnhub_calendar_dataB | IPO calendar, earnings calendar, economic events, and FDA meetings. Operations:
|
| finnhub_market_eventsC | Market holidays, analyst upgrades/downgrades, and M&A activity. Operations:
|
| finnhub_project_createB | Create project workspaces for organizing data. Operations:
|
| finnhub_project_listA | List all project workspaces with statistics. Operations:
|
| finnhub_job_statusC | Check status of background jobs. Operations:
|
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 15 tools
The tool categories are mostly distinct, but overlap exists between finnhub_stock_market_data's get_financials/get_earnings and finnhub_stock_fundamentals or finnhub_stock_estimates, as well as between market_events analyst upgrades and estimates recommendations. This creates ambiguity for an agent selecting the appropriate tool.
All 15 tools follow the consistent pattern 'finnhub_<domain>' using snake_case, such as finnhub_stock_estimates, finnhub_crypto_data, and finnhub_job_status. The naming is uniform and predictable.
15 tools is at the upper bound of the ideal range but suits the broad scope of financial data covered (stocks, crypto, forex, news, fundamentals, estimates, etc.). Some tools like finnhub_project_create and finnhub_project_list are ancillary, but the count is reasonable.
The tool set provides comprehensive coverage of financial data: real-time quotes, candles, fundamentals, estimates, news, technical analysis, insider trading, crypto, forex, and calendars. Minor gaps include missing project delete/update operations and some redundant data retrieval paths (e.g., get_financials vs get_basic_financials).