Financial Datasets

What Financial Datasets does

Financial Datasets provides MCP access to financial data sourced through financialdatasets.ai and routed by the Pipeworx gateway. The integration focuses on SEC-related company and ownership records rather than broad market-data coverage.

Agents can investigate which institutions hold a stock, inspect the long positions reported by a particular institutional filer, review recent insider activity, or retrieve a company's latest SEC filings. Results include structured fields such as tickers, investor names, shares, market values, report periods, transaction details, filing dates, and document URLs.

The repository describes the integration as an independent, unofficial connection to the upstream provider.

How it works

A hosted MCP client can connect to the pack endpoint:

{
  "mcpServers": {
    "financial-datasets": {
      "url": "https://gateway.pipeworx.io/financial-datasets/mcp"
    }
  }
}

The endpoint lists the pack's tools along with shared Pipeworx gateway tools. Those shared tools include ask_pipeworx, which can route a natural-language question across the wider Pipeworx catalog. The full gateway is also available at https://gateway.pipeworx.io/mcp when an agent should access all connected packs directly.

For local stdio use, the npm package starts a bridge that forwards requests to the same hosted endpoint. The bridge requires network access and has no offline mode.

Setup and configuration

Add the hosted URL to an MCP client, or run the local bridge with npx:

{
  "mcpServers": {
    "financial-datasets": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-financial-datasets"]
    }
  }
}

The upstream data tools accept an _apiKey argument. The local bridge can also authenticate to Pipeworx with PIPEWORX_API_KEY:

{
  "env": {
    "PIPEWORX_API_KEY": "<your key>"
  }
}

Anonymous bridge use is capped at 50 calls per day. A free Pipeworx account raises the allowance to 200 calls per day. The key is sent as a Bearer token, and calls are metered and billed in the same way as hosted connections.

Set PIPEWORX_META_TOOLS=1 in the local bridge configuration if the connection should list the shared Pipeworx tools in addition to the Financial Datasets tools. Proxy users may need NODE_USE_ENV_PROXY=1 because Node's built-in fetch does not automatically read HTTPS_PROXY.

Tools and capabilities

• fd_institutional_holders finds institutional investors reporting holdings in a ticker's latest SEC Form 13F. It returns investor names, shares, market values, and report periods.
• fd_investor_portfolio returns the long positions reported in an institutional filer's latest Form 13F. The filer is identified with a 10-digit, zero-padded SEC CIK.
• fd_insider_transactions retrieves recent purchases and sales reported by officers, directors, and 10% or greater owners in SEC Forms 3, 4, and 5. Results include the insider, title, transaction type, shares, price, date, and board-director status.
• fd_filings retrieves recent company filings such as 10-K, 10-Q, 8-K, 20-F, and 6-K records, including filing type, report period, filing date, and document URL. An optional filing_type filter narrows the results.

The tools support a limit argument in the examples, allowing callers to control the number of returned records.

Limitations and notes

This integration depends on the remote Pipeworx gateway and the upstream financial data service, so it cannot operate offline. A hosted pack endpoint also exposes shared gateway meta-tools, increasing the tool list beyond the four Financial Datasets-specific tools. The local bridge lists only the pack tools unless meta-tools are enabled.

Use a fund's SEC CIK, not just its common name, with fd_investor_portfolio. For example, Berkshire Hathaway is represented by 0001067983. API-key usage and request allowances apply when calling the data tools through the gateway.