# StockMarketScan (remote · mcp.stockmarketscan.com)

18 tools for US stock screeners, chart patterns, options flow signals and equities research.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.stockmarketscan.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-stockmarketscan-mcp-server/mcp.md), [page](https://verifymcp.io/servers/com-stockmarketscan-mcp-server/mcp)

## Channel facts

- Endpoint: `https://mcp.stockmarketscan.com/mcp`
- Transports: `sse`
- Auth: `required`
- Version: `1.0.5`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 40/100
  - Verified sse transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3331 tokens (~166/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-stockmarketscan-mcp-server https://mcp.stockmarketscan.com/mcp
```

### Codex

```toml
[mcp_servers.com-stockmarketscan-mcp-server]
url = "https://mcp.stockmarketscan.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-stockmarketscan-mcp-server": {
      "type": "remote",
      "url": "https://mcp.stockmarketscan.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-stockmarketscan-mcp-server --url https://mcp.stockmarketscan.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-stockmarketscan-mcp-server:
    url: "https://mcp.stockmarketscan.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-stockmarketscan-mcp-server": {
      "type": "http",
      "url": "https://mcp.stockmarketscan.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 65, +1)

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

### 2026-07-31 (score 64, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 63, +1)

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

### 2026-07-27 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 61)

First indexed and scored.

## MCP tools (20)

### `ping` (~38 tokens)

Minimal sanity check. Returns { status, version, timestamp, cache_size }. No auth needed. Use this to verify the MCP server is reachable and responsive.

### `list_screeners` (~81 tokens)

Return metadata for all 24 stock screeners on the platform, including each screener's slug, name, description, category, and tier. Use this to discover which screeners are available before calling get_screener_data. Call this once per session — the list changes very rarely. Returns { tier, total, accessible, screeners: [...] }.

### `get_screener_data` (~217 tokens)

Return the current rows of a single stock screener for its latest data date. Use this when the user asks about a specific screener like 'hot prospects' or 'golden cross'. Common slugs: hot-prospects, golden-cross, death-cross, rsi-oversold, rsi-overbought, defensive-stocks, dividend-prospects, j-pattern, nearing-6-month-highs, week-52-high-top-picks, top-penny-pops, strong-volume-gains, top-tech-stocks, fundamentally-fine, income-and-growth, best-reits. If you don't know the slug, call list_screeners first. Returns { screener, pagination, data: [stock rows] }.

Input parameters:

- `limit` (integer): Rows per page (max 500)
- `page` (integer): Page number (1-based)
- `slug` (string, required): The screener slug, e.g. 'hot-prospects', 'golden-cross', 'rsi-oversold'

### `search_stocks_in_screeners` (~155 tokens)

Find stocks that appear in multiple screeners simultaneously. Powerful for high-confidence picks where the user wants confluence across strategies. Use when the user asks 'which stocks are in both X and Y' or 'find stocks in 3+ bullish screeners'. Returns { screeners_queried, mode, count, symbols: [{symbol, screeners, match_count}] }. Intersection mode returns only stocks in ALL listed screeners; union returns stocks in ANY.

Input parameters:

- `limit` (integer)
- `mode` (string): intersection = stocks in ALL screeners; union = stocks in ANY screener
- `screener_slugs` (array, required): List of screener slugs to query (1-24)

### `get_chart_patterns` (~182 tokens)

Return all chart patterns currently detected for a single stock symbol. Detectable pattern ids: double_top, double_bottom, triple_top, triple_bottom, head_shoulders, inv_head_shoulders, round_bottom, cup_handle, asc_triangle, desc_triangle, sym_triangle, channel_up, channel_down, rectangle, flag, wedge_rising, wedge_falling, abcd, gartley, bat, butterfly, crab, impulse_wave, corrective_wave. Use when the user asks 'what patterns does X have' or 'is X forming a head and shoulders'. Requires a Basic or Pro API key. Returns { symbol, interval, computedAt, candleCount, patterns: [...] }. Empty patterns array if none detected.

Input parameters:

- `interval` (string): Chart interval
- `symbol` (string, required): Stock ticker, e.g. AAPL, TSLA, MSFT

### `search_patterns` (~247 tokens)

Find all stocks across one or more screeners that currently exhibit specific chart patterns. Much faster than calling get_chart_patterns in a loop. Use when the user asks 'which stocks have a cup and handle' or 'find me hot prospects with bullish reversal patterns'. Requires a Basic or Pro API key. Results are capped per screener group via `limit` (default 100); capped groups carry `truncated: true`. Returns { interval, selectedPatterns, totalUniqueStocks, groups: [...] }.

Input parameters:

- `interval` (string): Chart interval
- `limit` (integer): Max matching stocks per screener group (default 100)
- `pattern_ids` (array): Pattern ids to filter by. Empty = all patterns. Valid ids: double_top, double_bottom, triple_top, triple_bottom, head_shoulders, inv_head_shoulders, round_bottom, cup_handle, asc_triangle, desc_trian…
- `screener_slugs` (array, required): Screener slugs to search within

### `get_options_flow_overview` (~201 tokens)

Return the daily options flow table for one trading day — aggregated call/put volume, premium, implied volatility, and consecutive-day streaks for every notable symbol. Use when the user asks 'what's the options flow today' or 'show me the top premium plays'. Each row includes call_put_volume_ratio (bullish if > 1.0), consecutive_days (streak length), total_premium (dollar size), call_avg_iv/put_avg_iv. Returns { date, sort, limit, data: [...], stats, dates }. Tier: Pro only — Basic users get 403.

Input parameters:

- `date` (string): Trading day (YYYY-MM-DD). Default = latest available day.
- `limit` (integer): Rows to return (max 500)
- `sort` (string): Sort order: streak=longest streaks first, volume=highest volume, callput=most extreme C/P, premium=biggest dollar

### `get_options_flow_timeline` (~95 tokens)

Return the historical options flow for a single stock — most recent days first. Use when the user asks 'show me X's options flow history' or 'how long has X been bullish'. Returns { symbol, limit, count, data: [daily rows, newest first] }. Tier: Pro only.

Input parameters:

- `limit` (integer): Days of history (max 365)
- `symbol` (string, required): Stock ticker

### `get_options_flow_ranked` (~197 tokens)

Return ranked options flow entries for a date range — the entries that stand out by long consecutive-day streaks, large premium, and screener confluence. Each entry includes data-only performance tracking measured from a realistic entry reference: entry_price = open of the trading day AFTER signal_date (the close of signal_date is unreachable for live trading). max_gain_pct/max_drawdown_pct/price_change_pct are computed against entry_price; if that day's US open hasn't happened yet, these fields and entry_price are null ('pending'). This is descriptive market data for your own research, not a recommendation. If date_from/date_to omitted, returns last 60 days. Returns { count, signals: [...] }. Tier: Pro only.

Input parameters:

- `date_from` (string): Start date (YYYY-MM-DD)
- `date_to` (string): End date (YYYY-MM-DD)
- `limit` (integer): Max signals returned (default 500)

### `get_options_flow_sentiment` (~206 tokens)

Return daily options market sentiment — one row per trading day. Combines NYSE/NASDAQ market breadth (advance/decline + new highs/lows) with the market-wide call/put ratio. Each row includes market_breadth_score (0-100), market_call_put_ratio, the daily filter context (bullish_only/bearish_only/mixed), bullish_count/bearish_count of signals that day, plus a derived sentiment_score (0-100) and sentiment_label (bullish/neutral/bearish). Use when the user asks 'what's market sentiment today', 'how bullish is the market', 'show me sentiment over the last week'. If date_from/date_to omitted, returns last 60 days. Returns { dateFrom, dateTo, count, data: [...] }. Tier: Pro only.

Input parameters:

- `date_from` (string): Start date (YYYY-MM-DD)
- `date_to` (string): End date (YYYY-MM-DD)

### `get_unusual_options_activity` (~152 tokens)

Return individual options contracts flagged as unusual (Vol/OI > 1.5). Each row is one contract, not one stock. Use when the user wants contract-level detail. Filter by symbol, side (call/put/both), minimum vol/oi, minimum premium, or max days to expiration. For aggregated stock-level flow use get_options_flow_overview instead. Returns { date, count, contracts: [...] }.

Input parameters:

- `limit` (integer)
- `max_dte` (integer)
- `min_premium_usd` (number)
- `min_vol_oi` (number)
- `side` (string)
- `symbol` (string): Filter to one symbol

### `get_stock_info` (~105 tokens)

Return basic metadata for a stock — full company name, exchange, industry, last close price, and percent change. Use this when you first encounter a symbol and need to identify it. Lighter than get_stock_report (composite) or get_candles (full history). Returns { symbol, symbol_name, last_price, percent_change, exchange, industry }. Returns NOT_FOUND for unknown tickers.

Input parameters:

- `symbol` (string, required): Stock ticker, e.g. AAPL

### `get_candles` (~178 tokens)

Return OHLCV price candles for a single stock. Use when you need price history to compute indicators or answer 'how much is X up this month'. time is a Unix epoch in seconds (UTC midnight for daily). Default range is 6mo. Use larger ranges like '1y' or '2y' only when the user explicitly asks for long history — max range is 20 years. Returns { symbol, interval, range, count, data: [{time, open, high, low, close, volume}] }.

Input parameters:

- `interval` (string): Daily or weekly candles
- `range` (string): Range: 1d, 5d, 1y, 2y, 5y, max, or {N}mo (1-240)
- `symbol` (string, required): Stock ticker

### `search_stocks` (~126 tokens)

Search for stocks by ticker prefix or company name. THE tool to use when the ticker is unknown ('what's the symbol for Palantir?') or ambiguous — resolve the name to a symbol here, then use get_stock_info / get_stock_report with the symbol. No API key required. Returns { query, count, data: [{symbol, name}] } ordered by best match.

Input parameters:

- `limit` (integer): Max results (default 10)
- `query` (string, required): Symbol prefix or part of the company name, e.g. 'Apple' or 'NVD'

### `get_stock_report` (~201 tokens)

Return a comprehensive report on a single stock in one call — metadata, screener appearances, chart patterns, options flow, signal status, price summary, and upcoming earnings. THIS IS THE PREFERRED FIRST TOOL when a user asks about a single stock. It replaces 5-7 separate tool calls (get_stock_info + get_chart_patterns + get_options_flow_timeline + get_options_flow_ranked + screener lookups + get_candles). Do NOT also call the primitives after calling this — the composite already has everything. Parallel fetch under the hood, graceful partial failures (if one source errors, that section returns null with a note). Returns { symbol, info, screeners, patterns, options_flow, signal, candle_summary, upcoming_earnings, overall_bias }. overall_bias is a heuristic hint, not financial advice.

Input parameters:

- `interval` (string): Pattern detection interval
- `symbol` (string, required): Stock ticker, e.g. AAPL

### `search_setups` (~155 tokens)

Find the strongest trading setups today by combining options flow signals and screener confluence into a ranked list. Use when the user asks 'what should I trade today', 'best setups', 'top bullish plays'. Returns a ranked list with a composite score (signal strength + screener confluence + streak length). Present the top 3-5 to the user with narrative context, don't dump the raw JSON. Use get_stock_report if the user wants to dig deeper into any specific result. Returns { side, date, count, setups: [{symbol, score, signal, screeners_hit, ...}] }.

Input parameters:

- `limit` (integer): Max setups to return
- `side` (string): Side of setups to return

### `get_market_momentum` (~148 tokens)

Return NYSE and NASDAQ market breadth data — advancing/declining issues, new highs/lows, percent advancing. Use when the user asks 'how's the market today' or 'is breadth strong'. Default (no params): last 7 trading days. Returns { dates, count, data: [{exchange, advancing_issues, declining_issues, new_highs, new_lows, percent_advancing_issues, data_date}] }. Two rows per date (NYSE + NASDAQ). Tier: Basic+.

Input parameters:

- `date` (string): Single day (YYYY-MM-DD)
- `date_from` (string): Range start
- `date_to` (string): Range end

### `get_trends` (~118 tokens)

Return AI-detected trending topics in tech & science, patents, or funding events. Use when the user asks 'what's trending in tech' or 'show me patent trends'. Returns { category, count, trends: [{date, topic, weight}] } where weight is 0-1. Tier: Pro only.

Input parameters:

- `category` (string): Trend category
- `date` (string): Exact date lookup
- `days` (integer): Lookback window
- `latest` (boolean): If true, only return most recent day

### `get_trend_connections` (~121 tokens)

Return AI-computed connections between trending topics across categories (tech → patents, tech → funding, etc). Useful for spotting meta-trends. Use when the user asks 'what trends are connected' or 'show me cross-category signals'. Returns { count, connections: [{source_category, source_topic, target_category, target_topic, strength, rationale}] }. Tier: Pro only.

Input parameters:

- `date` (string)
- `days` (integer)
- `latest` (boolean)
- `limit` (integer): Max connections returned (default 200)

### `explain_concept` (~137 tokens)

Return a plain-language explanation of a platform-specific term, metric, or screener. Use ONLY for terms that are specific to StockMarketScan (e.g. 'strength_score' which is our internal scoring, or 'hot_prospects' which is our curated screener). Do NOT use for generic finance terms the model already knows — answer those directly. Returns { term, title, explanation, interpretation, related_terms }.

Input parameters:

- `term` (string, required): Term to explain, e.g. 'call_put_ratio', 'golden_cross', 'consecutive_days', 'strength_score', 'vol_oi_ratio', 'streak'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-stockmarketscan-mcp-server/mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 62
- 2026-07-29: 63
- 2026-07-28: 62
- 2026-07-27: 62
- 2026-07-26: 61

## Links

- Remote endpoint: https://mcp.stockmarketscan.com/mcp
- Authorisation metadata: https://mcp.stockmarketscan.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/stockmarketscan/mcp-server
- Website: https://stockmarketscan.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-stockmarketscan-mcp-server/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-stockmarketscan-mcp-server/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-stockmarketscan-mcp-server/mcp