Eugene Data Labs MCP Server

Eugene Data Labs MCP server exists for a simple reason — assistants are far more useful when they can act on Eugene Data Labs directly instead of describing what you should do. The first MCP-native financial data platform. One tool call gets you normalized SEC financials, 50+ computed ratios, live prices, technicals, crypto, and macro data — all with full provenance tracking. Built with async HTTP, persistent.

What the assistant can call

Once Eugene Data Labs is connected, these are the calls the assistant has available:

• sec — All SEC EDGAR data — 19 extract types via one tool
• economics — FRED macro data (inflation, employment, GDP, housing, rates)
• screener — Stock screening by sector, market cap, price, volume, beta
• crypto — Live crypto quotes (BTC, ETH, SOL, etc.)
• caps — Lists all capabilities and parameters
• Examples — The Examples tool exposed by this server

Configuration and credentials

You will need 2 environment variables: FMP_API_KEY, FRED_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Eugene Data Labs's toolset — sec, economics, screener and 3 more — is a fair guide to whether it matches your workflow. It is maintained by matthew-anyiam; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the eugene data labs mcp server does with a few real requests.