Fffinstill MCP Server

Fffinstill MCP server exists for a simple reason — assistants are far more useful when they can act on Fffinstill directly instead of describing what you should do. MCP server for fffinstill — investment analysis for 2,260+ US equities.

What you get

• 69 tools — — Stock analysis, screening, portfolio analytics, macro indicators, ML predictions, insider/congressional trades, alternative data, risk metrics, 18 academic factor models, and 13 Business-exclusive tools
• 7 resources — — Market signal, macro regime, Fear & Greed, sector overview, company summaries
• 15 prompts — — Pre-built workflows for stock analysis, comparison, screening, macro outlook, portfolio health, alternative data, market dashboard, deep value, risk assessment, growth momentum, income analysis, factor models, insider intelligence

What the assistant can call

Once Fffinstill is connected, these are the calls the assistant has available:

• Cursor — The Cursor tool exposed by this server

Configuration and credentials

You will need one environment variable: FINSTILL_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

The server ships on npm as @fffinstill/mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Fffinstill's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by alraico; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fffinstill's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

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 fffinstill mcp server does with a few real requests.