{
  "markdown": "# Finnhub — Stock, Crypto, Forex Data\n\nFinnhub's REST API. Real-time stock quotes, fundamentals, earnings, news, alternative data (insider transactions, sentiment, ETF holdings), economic data, crypto, and forex. Comprehensive market data with a strong free tier.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nWhere [Alpha Vantage](/docs/reference/alphavantage) is solid for fundamentals + technical, Finnhub is stronger for real-time quotes (1-minute resolution on free), insider transactions, news/sentiment, and international markets. For finance agents that need price data alongside news flow and insider activity, Finnhub is fit-for-purpose.\n\nCommon flows:\n\n- **Quote.** Real-time (or 15-min delayed on free tier) stock quote.\n- **Company news.** Recent news for a ticker with sentiment scoring.\n- **Insider transactions.** Form 4 filings with timing and dollar amounts (also see [insider-trading](/docs/reference/insider-trading) pack which is SEC-EDGAR-direct).\n- **Earnings.** Upcoming earnings calendar, surprise history, EPS estimates.\n- **International symbols.** European, Asian, emerging-market tickers (where Alpha Vantage gets thinner).\n\n## Auth\n\nFree key from https://finnhub.io/dashboard. Free tier: 60 API calls/minute. Pass via `_apiKey`.\n\nHigher tiers ($50-200/mo) unlock real-time data, longer historical, and rate limits suitable for production. The free tier is sufficient for most agent research.\n\n## When to use Finnhub vs. Alpha Vantage\n\n| Need | Better source |\n|---|---|\n| Quotes | Either; Finnhub real-time-er on free tier |\n| Income statement / balance sheet | Alpha Vantage (cleaner schema) |\n| Insider transactions | Finnhub or insider-trading pack |\n| Company news with sentiment | Finnhub |\n| Earnings calendar | Finnhub |\n| International coverage | Finnhub |\n| Technical indicators | Alpha Vantage |\n| ETF holdings | Finnhub |\n\nFor richest coverage, Pipeworx agents often mount both.\n\n## Common pitfalls\n\n- **Symbol conventions.** US tickers are simple (AAPL); international markets need exchange suffixes (NESN.SW for Nestlé on Swiss exchange). Finnhub has a symbol search.\n- **Free tier real-time delay.** \"Real-time\" on free is essentially current; on paid it's actually live. For agent research, free is fine. For trading, paid.\n- **News sentiment is heuristic.** Finnhub computes sentiment with NLP — it's directionally useful but noisy. Don't treat as ground truth; useful as a signal.\n- **Insider transaction lag.** SEC requires Form 4 filing within 2 business days of the transaction. Finnhub picks them up shortly after. Real-time alerting requires either polling or a separate real-time SEC feed.\n- **Estimates vs. actuals.** Finnhub provides analyst consensus estimates; mixing them with actuals in plots requires labeling carefully.\n- **Free-tier coverage holes.** Some smaller caps and OTC stocks have limited Finnhub coverage on free. Verify the data exists for your target tickers before designing flows around it.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"finnhub\": {\n      \"url\": \"https://gateway.pipeworx.io/finnhub/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/finnhub/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Finnhub data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5092,
  "sha": "10aaa55919c63ba76d1495e8c7118c2c6eb994d755417327787d9a60368828a4",
  "repo_slug": "pipeworx-io/mcp-finnhub",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_finnhub_1cec21b6/readme"
}