English Français العربية

Gurufocus

Official registry Other

GuruFocus MCP — wraps the GuruFocus Data API (gurufocus.com/data-api)

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http gurufocus 'https://gateway.pipeworx.io/gurufocus/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "gurufocus": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/gurufocus/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-gurufocus
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-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

ToolDescription
gurufocus_summaryGet 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_gurusGet 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_insiderGet 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_priceGet 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

Frequently asked questions

What is Gurufocus?

GuruFocus MCP — wraps the GuruFocus Data API (gurufocus.com/data-api)

How do I install Gurufocus?

It runs as a remote server. In Claude Code: claude mcp add --transport http gurufocus 'https://gateway.pipeworx.io/gurufocus/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Gurufocus need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Gurufocus open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Gurufocus?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.