pickfit

BrowseMCP servers

tiingo-mcp

Rust MCP server that provides Tiingo stock, forex, crypto, news and fundamentals data.

Tested on macOS and Linux

Use it

macOS arm64

You need first

  • Runtimes: Rust >=1.88
  • Needs the network
  • Keys or accounts: Tiingo API key
  1. brew tap and install tiingo-mcp 2.3.0

    brew tap major7apps/tiingo-mcp https://github.com/major7apps/tiingo-mcp 2>&1 && brew install major7apps/tiingo-mcp/tiingo-mcp

Check that it works

tiingo-mcp --version 2>&1

The output should contain “tiingo-mcp 2.3.0”.

Add it to your agent

claude mcp add tiingo-mcp -e TIINGO_API_KEY='<TIINGO_API_KEY>' -- tiingo-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "tiingo-mcp": {
      "command": "tiingo-mcp",
      "args": [],
      "env": {
        "TIINGO_API_KEY": "<TIINGO_API_KEY>"
      }
    }
  }
}

You fill in

  • TIINGO_API_KEY: Tiingo API key (required)

Ask the user for TIINGO_API_KEY; pickfit never had a value, so these are placeholders.

Add tiingo-mcp as an MCP server in your MCP client, and the client will list its Tiingo data tools.

Linux x86_64

You need first

  • Runtimes: Rust >=1.88
  • Needs the network
  • Keys or accounts: Tiingo API key
  1. Download installer script

    curl --proto '=https' --tlsv1.2 -LsSf https://github.com/major7apps/tiingo-mcp/releases/latest/download/tiingo-mcp-installer.sh -o /tmp/tiingo-mcp-installer.sh
  2. Run installer script

    sh /tmp/tiingo-mcp-installer.sh && ~/.cargo/bin/tiingo-mcp --version
  3. Link binary onto PATH

    mkdir -p ~/.local/bin && ln -sf ~/.cargo/bin/tiingo-mcp ~/.local/bin/tiingo-mcp && export PATH="$HOME/.local/bin:$PATH"

Check that it works

tiingo-mcp --version

The output should contain “tiingo-mcp 2.3.0”.

Add it to your agent

claude mcp add tiingo-mcp -e TIINGO_API_KEY='<TIINGO_API_KEY>' -- tiingo-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "tiingo-mcp": {
      "command": "tiingo-mcp",
      "args": [],
      "env": {
        "TIINGO_API_KEY": "<TIINGO_API_KEY>"
      }
    }
  }
}

You fill in

  • TIINGO_API_KEY: Tiingo API key (required)

Ask the user for TIINGO_API_KEY; pickfit never had a value, so these are placeholders.

Add tiingo-mcp as an MCP server in your MCP client, and the client will list its Tiingo data tools.

What it does

  • Get stock, forex and crypto prices
    Not tested
  • Search financial news articles
    Not tested
  • Get company fundamentals and financial statements
    Not tested
  • Subscribe to live market data feeds
    Not tested

How far pickfit got

macOS arm64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Connects
  3. 0 of 4 features work
  4. Works offline

Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • retrieve historical EOD stock prices and volume
  • get current forex bid and ask quotes
  • get current crypto prices
  • search financial news articles
  • retrieve company financial statements

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 2.3.0

An MCP client handshake over stdio listed 38 tools.

Linux x86_64

An MCP client connects and lists its tools

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 2.3.0

An MCP client handshake over stdio listed 38 tools.

Differences the test machine hit

  • README: install script installs into Cargo binary directory and to follow instructions to update PATH
    In the test: installer placed binary in ~/.cargo/bin which is not on this box's PATH (starts with ~/.local/bin), so linked it to ~/.local/bin/tiingo-mcp
  • README: curl installer script from releases/latest/download
    In the test: installer script downloads and verifies a prebuilt binary tarball at run time, which cannot be read as text

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.