Financial Signals MCP Server

Financial Signals MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Derived financial intelligence: insider patterns, earnings, institutional & ratio signals.

What you get

screen_stocks and company_profile expose a proprietary composite_value_score (0-100) — a transparent blend of: valuation vs. sector, growth, margin quality, insider sentiment, institutional momentum, and earnings consistency. Sort screen_stocks by it and you're using a ranking nobody else computes.

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. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Financial Signals MCP is connected, these are the calls the assistant has available:

• insider_activity — $0.01
• earnings_check — $0.01
• institutional_moves — $0.01
• screen_stocks — $0.01
• sector_snapshot — $0.01
• macro_dashboard — free
• company_profile — $0.01
• anomaly_alert — $0.02
• daily_brief — $25
• brief_summary — $0.50
• mint_info — free

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.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Financial Signals MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the financial signals mcp mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Financial Signals MCP's toolset — insider_activity, earnings_check, institutional_moves and 8 more — is a fair guide to whether it matches your workflow. It is maintained by FoundryNet; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.