Tiingo (community)

major7apps (OSS) · Market & Financial Data

MCP ServerCommunity

Community Rust MCP server for Tiingo market data with 38 tools: end-of-day, IEX intraday and consolidated equity prices, forex, crypto, mutual fund and ETF fee data, news, fundamentals, dividends and splits, plus bounded live market-data subscriptions. Prebuilt binaries, Homebrew, Windows MSI, Claude Desktop bundles and crates.io installs are available.

market dataequity pricesforexcryptofundamentalsfinancial newsfund feesrust

Status

Community

Auth

API key

Hosting

Local

Community rating

Not rated yet

Role

Source

Provides data. A read-only feed from one provider; it answers questions, doesn't act, and doesn't expect other servers alongside it. More on Source servers → All seven roles →

Open documentation →

Caveats

Community-reported capabilities and installation options have not been independently verified. This is a community-maintained project with an MIT license.
The documented tools retrieve data and manage market-data subscriptions; no order placement or account-record writes are documented.
Community-reported deployment uses a local stdio process with a Tiingo API key supplied through the MCP client. Requests connect to Tiingo, so local hosting does not mean all processing stays local; no remote MCP transport is offered.
Community-reported access depends on the features enabled for the Tiingo key. Fund fee data requires enterprise or institutional access, certain IEX subscription levels require a direct market-data agreement, and requests consume quota or bandwidth.
Community-reported live subscriptions close at 2,048 events or 8 MiB, after 30 minutes, or after five minutes without client calls. Reaching a buffer limit requires starting a new subscription.
Community-reported consolidated equity, BOATS and forex datasets are beta, and asset search is early beta. BOATS is a separate add-on, not a combined 24-hour equity feed.
Start with read-only scopes and keep client-side approval prompts on until the connection is proven.

Rate this server

How to connect Tiingo (community)

Step 1

Local server, run it on your machine

Tiingo (community) runs locally over stdio. You need Node.js (for npx) or Python (for uvx) installed, then add the command below to your client's MCP config file.

Command

cargo install tiingo-mcp --locked

Client config snippet

{
  "mcpServers": {
    "8b8df76e-3206-4aa6-b544-4088fe4d7696": {
      "command": "cargo",
      "args": [
        "install",
        "tiingo-mcp",
        "--locked"
      ]
    }
  }
}

Step 2

Authenticate with API key

Create a key in the vendor's dashboard and store it as an environment variable in your client config. Never paste it into a chat window.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Market & Financial Data.

Tax-lot and wash-sale check

A flag list before trades are placed.

Trade & RebalanceCustody & ClearingMarket & Financial Data

Read-only: for the proposed sells in <account>, review tax lots at the custodian and flag short-term gains, large realised gains, and any purchase in the last 30 days that could create a wash sale. Then use market-data tools to value each lot at the latest available price and to check for splits, mergers or other corporate actions that would change basis or share count. Output Symbol / Lot / Acquired / Basis / Market value / Gain-loss / Flag / Source. Do not place or modify trades. Tell me where the data may be delayed or incomplete.

Guardrail · Read-only. Confirm lot data with the custodian before acting on it.

Scenario comparison brief

A side-by-side read on two planning scenarios.

Financial PlanningFinancial PlanningMarket & Financial Data

Read-only: compare the existing plan for <client name> against the scenario <describe change, e.g. retire two years earlier>. Pull the plan's stored return, inflation and yield assumptions, then use market-data tools to show current comparable figures for the same inputs. Present outcome differences, an assumptions table of Plan assumption / Current market reading / Source / Date, and which assumption the result is most sensitive to. State every assumption explicitly. Do not save, overwrite or publish any scenario in the planning system.

Guardrail · Read-only. Plan illustrations are not advice, review before sharing.

Market context talking points

Three to five neutral talking points on recent market moves.

Client Review Meeting PrepWealth PlatformsMarket & Financial Data

Read-only: pull <client name>'s current holdings and sector or asset-class weights from the wealth platform, then use market-data tools to explain what moved those specific exposures over the last quarter. Return three to five neutral talking points, each tied to a holding or weight and to the market data behind it. No forecasts, no recommendations to buy or sell, no performance promises. Cite the source and date for both the holdings figure and the market figure so I can verify before I use it with a client.

Guardrail · Educational framing only. Avoid forward-looking or promissory language.

Read the full connection guide →