Market Data Analyzer

io.github.vpatser1Published by GitHub account vpatser1v2.1.4Updated Oct 24, 2026

Stock technical analysis (SMA, RSI, MACD), portfolio tracking, crypto analysis, screening

VerifiedSTDIODesktop onlyFinanceData & Analytics

Overview

AI-generated overview

A local MCP server that gives an assistant stock and crypto technical analysis, portfolio tracking, and screening tools.

What you can do
Market Data Analyzer runs locally and exposes tools for technical analysis of stocks and crypto, including indicators such as SMA, RSI and MACD. It also covers portfolio tracking and screening, so an assistant can compute indicators, follow holdings, and filter instruments on request. The manifest does not list individual tool names.
When to use it
Worth adding when you want an assistant to run technical indicator calculations, track a portfolio, or screen stocks and crypto during a conversation, rather than looking up prices manually. It is a desktop-only local process, so it suits a workstation setup.
Requirements
Runs as a local process over stdio, installed from the npm package market-data-analyzer, so Node.js and npm are needed. A LICENSE_KEY environment variable is used: a license key is emailed after purchase, and omitting it gives a free trial of 3 calls per tool. No other authentication is declared.
Before you install
The server is commercial: full use requires a purchased license key supplied through the LICENSE_KEY environment variable, and the free trial is limited to 3 calls per tool. Treat that key as a secret and avoid exposing it in logs or shared configuration. The manifest declares no write, send, or delete actions and no third-party data sharing beyond the license check.

Installation

In SourceWeft

  1. Open Market Data Analyzer 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.

Tools

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

Version history

1
  1. v2.1.4LatestSep 16, 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.