Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.vpatser1/market-data-analyzer

NPM · MARKET-DATA-ANALYZER · SCANNED SEP 24

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

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 529 tokens (~88/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.vpatser1/market-data-analyzer MCP server?

io.github.vpatser1/market-data-analyzer runs locally as an npm package, launched with npx -y market-data-analyzer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · market-data-analyzer

# add to Claude Code
claude mcp add vpatser1-market-data-analyzer -- npx -y market-data-analyzer
// .cursor/mcp.json
{
  "mcpServers": {
    "vpatser1-market-data-analyzer": {
      "command": "npx",
      "args": [
        "-y",
        "market-data-analyzer"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "vpatser1-market-data-analyzer": {
      "command": "npx",
      "args": [
        "-y",
        "market-data-analyzer"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add vpatser1-market-data-analyzer -- npx -y market-data-analyzer
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vpatser1-market-data-analyzer": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "market-data-analyzer"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vpatser1-market-data-analyzer --command npx --arg -y --arg market-data-analyzer
# ~/.hermes/config.yaml
mcp_servers:
  vpatser1-market-data-analyzer:
    command: "npx"
    args: ["-y", "market-data-analyzer"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "vpatser1-market-data-analyzer": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "market-data-analyzer"
      ]
    }
  }
}
# add to Vellum
assistant mcp add vpatser1-market-data-analyzer -t stdio -c npx -a -y market-data-analyzer
// mcp.json
{
  "mcpServers": {
    "vpatser1-market-data-analyzer": {
      "command": "npx",
      "args": [
        "-y",
        "market-data-analyzer"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Analysed npm/market-data-analyzer@2.1.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~529 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_portfolio ~64

Analyze a portfolio of holdings. Provide positions with symbol, shares, and average cost. Returns total value, P&L per position, allocation %, diversification score, and risk metrics. Fetches live prices from Yahoo Finance.

NameTypeReqDescription
holdingsarrayyesArray of portfolio holdings

No output schema declared.

No examples provided.

analyze_stock ~70

Deep analysis of a stock symbol: price, moving averages (SMA 20/50/200), RSI, MACD, support/resistance levels. Uses live Yahoo Finance data.

NameTypeReqDescription
symbolstringyesStock ticker symbol (e.g. 'AAPL', 'MSFT', 'TSLA')

No output schema declared.

No examples provided.

compare_assets ~87

Compare 2-5 assets side by side: returns, volatility, correlation, Sharpe ratio approximation over a given period. Uses Yahoo Finance historical data.

NameTypeReqDescription
periodstringComparison period (default: '6mo')
symbolsarrayyesArray of 2-5 ticker symbols to compare (e.g. ['AAPL', 'MSFT', 'GOOGL'])

No output schema declared.

No examples provided.

crypto_analysis ~70

Crypto-specific analysis: price, 24h volume, market dominance, fear/greed index approximation, supply metrics, ATH/ATL data. Uses CoinGecko free API.

NameTypeReqDescription
symbolstringyesCryptocurrency symbol or name (e.g. 'BTC', 'ETH', 'SOL', 'bitcoin')

No output schema declared.

No examples provided.

market_overview ~50

Current market snapshot: major indices (S&P 500, NASDAQ, DOW), sector performance via ETFs, market breadth indicators, VIX, crypto, and commodities. Live data from Yahoo Finance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

screen_stocks ~188

Screen stocks by criteria: market cap range, P/E ratio, sector, volume threshold. Returns top matches with key metrics. Fetches live data from Yahoo Finance for ~70 popular stocks.

NameTypeReqDescription
limitintegerMax results to return (default: 25)
max_market_capnumberMaximum market cap in USD
max_penumberMaximum trailing P/E ratio
max_pricenumberMaximum stock price
min_market_capnumberMinimum market cap in USD (e.g. 1000000000 for $1B)
min_penumberMinimum trailing P/E ratio
min_pricenumberMinimum stock price
min_volumenumberMinimum daily trading volume
sectorstringSector filter (partial match, e.g. 'tech', 'health', 'energy')

No output schema declared.

No examples provided.

Common questions

What is the io.github.vpatser1/market-data-analyzer MCP server?

io.github.vpatser1/market-data-analyzer is an MCP server listed in the public MCP registry as io.github.vpatser1/market-data-analyzer. Stock technical analysis (SMA, RSI, MACD), portfolio tracking, crypto analysis, screening. This page covers its npm package (market-data-analyzer).

Is the io.github.vpatser1/market-data-analyzer MCP server safe to use?

io.github.vpatser1/market-data-analyzer scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.vpatser1/market-data-analyzer MCP server expose?

io.github.vpatser1/market-data-analyzer exposes 6 tools: analyze_stock, screen_stocks, analyze_portfolio, compare_assets, market_overview, crypto_analysis. Their descriptions and schemas cost roughly 529 tokens of context every time the server is loaded.

Is the io.github.vpatser1/market-data-analyzer MCP server still maintained?

io.github.vpatser1/market-data-analyzer is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.vpatser1/market-data-analyzer MCP server under?

io.github.vpatser1/market-data-analyzer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.