Back to Browse

Gurufocus MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://gateway.pipeworx.io/gurufocus/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (1397/1410 approved). 1 finding(s) downgraded by scanner intelligence.

40 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-pipeworx-io-gurufocus": {
      "url": "https://gateway.pipeworx.io/gurufocus/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

mcp-gurufocus

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

Part of Pipeworx — an MCP gateway connecting AI agents to 1663+ live data sources.

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 1663+ 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

Reviews

No reviews yet

Be the first to review this server!