About Gurufocus
Gurufocus wraps the GuruFocus Data API as an MCP service for users researching company fundamentals, investor holdings, insider trades, and prices. It can be accessed through the Pipeworx gateway or run locally over stdio.
Key features
- 01Retrieve company summaries, GF Score, and GF Value
- 02Review famous investors’ holding changes
- 03Query corporate insider trades
- 04Get historical OHLCV price bars
Use cases
- 01Assess a stock’s financial profile and valuation
- 02Track buying and selling by famous investors
- 03Inspect corporate insider transaction records
- 04Retrieve historical prices and trading volume
MCP support
It exposes GuruFocus tools for stock summaries, guru holding changes, insider trades, and historical prices to MCP clients. Connect through the Pipeworx gateway or run it as a local stdio MCP server.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/gurufocus/mcpclaude mcp add --transport http pipeworx-io-gurufocus https://gateway.pipeworx.io/gurufocus/mcp{"mcpServers":{"pipeworx-io-gurufocus":{"type":"http","url":"https://gateway.pipeworx.io/gurufocus/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-gurufocus":{"type":"http","url":"https://gateway.pipeworx.io/gurufocus/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-gurufocus":{"type":"http","url":"https://gateway.pipeworx.io/gurufocus/mcp"}}}{"mcpServers":{"pipeworx-io-gurufocus":{"serverUrl":"https://gateway.pipeworx.io/gurufocus/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcp-gurufocus
GuruFocus MCP — wraps the GuruFocus Data API (gurufocus.com/data-api)
Part of Pipeworx — an MCP gateway connecting AI agents to 1881+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
gurufocus_summary | Get a GuruFocus stock summary/overview for a symbol — company info plus proprietary rankings including GF Score (0-100), GF Value (fair-value estimate), and sub-rankings (financial strength, profitability, growth, momentum, predictability). Example: gurufocus_summary({ symbol: "AAPL", _apiKey: "your-token" }) |
gurufocus_gurus | Get guru holding-change records for a symbol — which famous investors (gurus) bought or sold. Returns guru name, action, share-change signal, current shares, portfolio date, and position weight. Example: gurufocus_gurus({ symbol: "AAPL", _apiKey: "your-token" }) |
gurufocus_insider | Get insider trades for a symbol — corporate insiders buying/selling. Returns insider identity, role/position, transaction date, trade type, share count, execution price, and resulting ownership. Supports pagination. Example: gurufocus_insider({ symbol: "AAPL", page: 1, _apiKey: "your-token" }) |
gurufocus_price | Get historical OHLCV price bars for a symbol — open, high, low, close, volume time series. Example: gurufocus_price({ symbol: "AAPL", _apiKey: "your-token" }) |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"gurufocus": {
"url": "https://gateway.pipeworx.io/gurufocus/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/gurufocus/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1881+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/gurufocus_summary. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"gurufocus": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-gurufocus"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-gurufocus
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Gurufocus data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.