Tiingo Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

MCP server for Tiingo: stocks, forex, crypto. Needs a free API token.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server that connects an assistant to Tiingo market data for stocks, forex and crypto.

What you can do
  • Provides access to Tiingo market data covering stocks, forex and cryptocurrency.
  • No tool list is published, so the exact queries and endpoints available are not documented here.
  • Runs as a local stdio process started by the assistant on the user's machine.
When to use it
Worth adding when you want an assistant to pull Tiingo market data for stocks, forex or crypto while working on your own machine, and you already have or can get a Tiingo API token.
Requirements
Runs locally over stdio, installed from the npm package tiingo-mcp, so a Node.js runtime is needed. A Tiingo API token is required; the registry description says a free token is enough. The manifest declares no environment variables or headers, so how the token is supplied is not documented here. Network access to Tiingo is implied.
Before you install
You must supply a Tiingo API token, which is a credential; keep it out of shared configuration and logs. Requests go to Tiingo's third-party service. No tool list or README is available, so review the package before installing. Desktop only; no web execution.

Installation

In SourceWeft

  1. Open Tiingo Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.1LatestOct 17, 2026
  2. v1.0.0Sep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.