StockMarketScan
REMOTE · MCP.STOCKMARKETSCAN.COM
18 tools for US stock screeners, chart patterns, options flow signals and equities research.
Available components
Last scanned (21 hours ago)
Scores higher than 72% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3740 tokens (~187/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_chart_patterns” rewrote its description, which is the text the model reads security
- Tool “get_market_momentum” rewrote its description, which is the text the model reads security
- Tool “get_options_flow_overview” rewrote its description, which is the text the model reads security
- Tool “search_patterns” rewrote its description, which is the text the model reads security
- 30 Sept 26 0
- Tool “get_candles” rewrote its description, which is the text the model reads security
- Tool “explain_concept” rewrote its description, which is the text the model reads security
- Tool “get_chart_patterns” rewrote its description, which is the text the model reads security
- Tool “get_market_momentum” rewrote its description, which is the text the model reads security
- Tool “get_options_flow_overview” rewrote its description, which is the text the model reads security
- Tool “get_options_flow_ranked” rewrote its description, which is the text the model reads security
- Tool “get_options_flow_sentiment” rewrote its description, which is the text the model reads security
- Tool “get_options_flow_timeline” rewrote its description, which is the text the model reads security
- Tool “get_screener_data” rewrote its description, which is the text the model reads security
- Tool “get_stock_info” rewrote its description, which is the text the model reads security
- Tool “get_stock_report” rewrote its description, which is the text the model reads security
- Tool “get_trend_connections” rewrote its description, which is the text the model reads security
- Tool “get_trends” rewrote its description, which is the text the model reads security
- Tool “get_unusual_options_activity” rewrote its description, which is the text the model reads security
- Tool “list_screeners” rewrote its description, which is the text the model reads security
- Tool “search_patterns” rewrote its description, which is the text the model reads security
- Tool “search_setups” rewrote its description, which is the text the model reads security
- Tool “search_stocks” rewrote its description, which is the text the model reads security
- Tool “search_stocks_in_screeners” rewrote its description, which is the text the model reads security
- Schema quality: 166 → 187 ▼ functional
- “get_options_flow_overview” added an optional parameter “cursor” cosmetic
- “get_options_flow_ranked” added an optional parameter “cursor” cosmetic
- “get_options_flow_sentiment” added an optional parameter “cursor” cosmetic
- “get_options_flow_timeline” added an optional parameter “cursor” cosmetic
- “get_screener_data” added an optional parameter “cursor” cosmetic
- “get_unusual_options_activity” added an optional parameter “cursor” cosmetic
- “get_options_flow_ranked” reworded the description of “limit” cosmetic
- “get_screener_data” dropped the optional parameter “page” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://mcp.stockmarketscan.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stockmarketscan.com | CN=YE1,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5724eb1732ed92d5470966a49034d03a36b |
| SANs: *.stockmarketscan.com, stockmarketscan.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.stockmarketscan.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| stockmarketscan.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.stockmarketscan.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.stockmarketscan.com/mcp | HTTPS enforced | 301 | https://mcp.stockmarketscan.com/mcp |
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 →
explain_concept ~137
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | Term to explain, e.g. 'call_put_ratio', 'golden_cross', 'consecutive_days', 'strength_score', 'vol_oi_ratio', 'streak' |
No output schema declared.
No examples provided.
get_candles ~189
Return OHLCV price candles for a single stock, oldest first. Use when you need price history to compute indicators or answer 'how much is X up this month'. date is the trading day (YYYY-MM-DD; weekly candles use the Monday). 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 { data: [{ date, open, high, low, close, volume }], meta: { as_of, pagination: { total } } }.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Daily or weekly candles |
| range | string | – | Range: 1d, 5d, 1y, 2y, 5y, max, or {N}mo (1-240) |
| symbol | string | yes | Stock ticker |
No output schema declared.
No examples provided.
get_chart_patterns ~222
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 Pro or Enterprise API key. Returns { data: { symbol, interval, computed_at, candle_count, patterns: [{ id, name, type, category, confidence, points, lines, target_price, last_structural_point }] } } where type is the pattern direction (bullish, bearish, neutral). Empty patterns array if none detected.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Chart interval |
| symbol | string | yes | Stock ticker, e.g. AAPL, TSLA, MSFT |
No output schema declared.
No examples provided.
get_market_momentum ~200
Return NYSE and NASDAQ market breadth: advancing/declining/unchanged issues, their percentages, and new highs/lows. Use when the user asks 'how's the market today' or 'is breadth strong'. Default (no params): last 7 trading days. Send either date or date_from/date_to (either end may be omitted). Returns { data: [{ data_date, exchange, advancing_issues, declining_issues, unchanged_issues, percent_advancing_issues, percent_declining_issues, percent_unchanged_issues, new_highs, new_lows }], meta: { as_of } }; all counts and percents are numbers (63 means 63%). Two rows per date (NYSE + NASDAQ). Tier: Pro or Enterprise.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Single day (YYYY-MM-DD) |
| date_from | string | – | Range start |
| date_to | string | – | Range end |
No output schema declared.
No examples provided.
get_options_flow_overview ~222
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 largest premium'. Each row includes call_put_volume_ratio (> 1.0 means more call than put volume), consecutive_days (streak length), total_premium (dollar size), call_avg_iv/put_avg_iv. Returns { data: [...], meta: { as_of, market_stats, available_dates, pagination: { next_cursor } } }. Tier: Pro or Enterprise.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.pagination.next_cursor from the previous page |
| 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 |
No output schema declared.
No examples provided.
get_options_flow_ranked ~245
Return ranked options flow records for a date range: the records that stand out by long consecutive-day streaks, large premium, and screener confluence. Each record 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 not an available fill price). 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 { data: [...], meta: { as_of, pagination: { next_cursor }, parameters: { date_from, date_to } } }. Dates are YYYY-MM-DD and numbers are JSON numbers. Tier: Pro only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.pagination.next_cursor from the previous page |
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
| limit | integer | – | Max records returned (default 500) |
No output schema declared.
No examples provided.
get_options_flow_sentiment ~223
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 flow records 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 { data: [...], meta: { as_of, pagination } }. Tier: Pro only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.pagination.next_cursor from the previous page |
| date_from | string | – | Start date (YYYY-MM-DD) |
| date_to | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_options_flow_timeline ~117
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 { data: [daily rows, newest first], meta: { as_of, pagination: { next_cursor } } }. Tier: Pro only.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.pagination.next_cursor from the previous page |
| limit | integer | – | Days of history (max 365) |
| symbol | string | yes | Stock ticker |
No output schema declared.
No examples provided.
get_screener_data ~271
Return the rows of a single stock screener for its latest snapshot. 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. Numbers are JSON numbers (percent_change 1.25 means +1.25%), dates are YYYY-MM-DD. Returns { data: [rows], meta: { as_of, screener, pagination: { next_cursor, total } } }. For the next page pass meta.pagination.next_cursor as cursor.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.pagination.next_cursor from the previous page. Omit for the first page. |
| limit | integer | – | Rows per page (max 500) |
| slug | string | yes | The screener slug, e.g. 'hot-prospects', 'golden-cross', 'rsi-oversold' |
No output schema declared.
No examples provided.
get_stock_info ~127
Return basic metadata for a stock: full company name, exchange, industry, last price, and daily 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 { data: { symbol, symbol_name, last_price, percent_change, exchange, industry }, meta: { as_of } }; percent_change 1.27 means +1.27%. Returns NOT_FOUND for unknown tickers.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Stock ticker, e.g. AAPL |
No output schema declared.
No examples provided.
get_stock_report ~199
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, as_of, info, screeners, patterns, options_flow, signal, candle_summary, overall_bias }. overall_bias is a heuristic hint, not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | – | Pattern detection interval |
| symbol | string | yes | Stock ticker, e.g. AAPL |
No output schema declared.
No examples provided.
get_trend_connections ~138
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'. Use one of latest, date, or days. Returns { data: [{ date, source_category, source_topic, target_category, target_topic, strength, rationale }], meta: { as_of } }. Tier: Pro only.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | – |
| days | integer | – | – |
| latest | boolean | – | – |
| limit | integer | – | Max connections returned (default 200) |
No output schema declared.
No examples provided.
get_trends ~131
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'. Use one of latest, date, or days. Returns { data: [{ date, topic, weight }], meta: { as_of } } where weight is 0-1. Tier: Pro only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Trend category |
| date | string | – | Exact date lookup |
| days | integer | – | Lookback window |
| latest | boolean | – | If true, only return most recent day |
No output schema declared.
No examples provided.
get_unusual_options_activity ~171
Return individual options contracts flagged as unusual activity (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: [...], next_cursor }.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | meta.pagination.next_cursor from the previous page |
| limit | integer | – | – |
| max_dte | integer | – | – |
| min_premium_usd | number | – | – |
| min_vol_oi | number | – | – |
| side | string | – | – |
| symbol | string | – | Filter to one symbol |
No output schema declared.
No examples provided.
list_screeners ~122
Return metadata for all 24 stock screeners on the platform: slug, name, description, category, tier, whether the caller can read it, and its row fields with their JSON value types. Use this to discover which screeners are available before calling get_screener_data. Call this once per session; the list changes very rarely. Returns { data: [{ slug, name, description, category, tier, accessible, columns: [{ key, label, type, value_type }] }], meta: { caller_tier, total, accessible } }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ping ~38
Minimal sanity check. Returns { status, version, timestamp, cache_size }. No auth needed. Use this to verify the MCP server is reachable and responsive.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_patterns ~292
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 Pro or Enterprise API key; unknown slugs or pattern ids and screeners above the plan are errors. Results are capped per screener group via `limit` (default 100); capped groups carry truncated: true. Returns { data: [{ screener_slug, screener_name, count, truncated, stocks: [{ symbol, symbol_name, last_price, volume, data_date, matched_patterns }] }], meta: { total_unique_stocks } }.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Screener slugs to search within |
No output schema declared.
No examples provided.
search_setups ~152
List today's options flow records for one side (bullish or bearish), ranked by a descriptive composite score (strength score + consecutive-day streak + premium size). Use when the user asks which symbols had the most notable options flow today. This is descriptive market data, not a recommendation. Summarize the first few rows rather than dumping the raw JSON. Use get_stock_report to look at a single symbol in more detail. Returns { side, date, count, setups: [{ symbol, score, signal: { type, strength, consecutive_days, call_put_ratio, total_premium } }] }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max setups to return |
| side | string | – | Side of setups to return |
No output schema declared.
No examples provided.
search_stocks ~124
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 { data: [{ symbol, name }], meta } ordered by best match.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10) |
| query | string | yes | Symbol prefix or part of the company name, e.g. 'Apple' or 'NVD' |
No output schema declared.
No examples provided.
search_stocks_in_screeners ~149
Find stocks that appear in multiple screeners simultaneously. Useful for finding overlap across screeners. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| mode | string | – | intersection = stocks in ALL screeners; union = stocks in ANY screener |
| screener_slugs | array | yes | List of screener slugs to query (1-24) |
No output schema declared.
No examples provided.
How do I install the StockMarketScan MCP server?
StockMarketScan is a hosted endpoint at https://mcp.stockmarketscan.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.stockmarketscan.com
claude mcp add --transport http com-stockmarketscan-mcp-server 'https://mcp.stockmarketscan.com/mcp'
What is the StockMarketScan MCP server?
StockMarketScan is an MCP server listed in the public MCP registry as com.stockmarketscan/mcp-server. 18 tools for US stock screeners, chart patterns, options flow signals and equities research. This page covers its hosted endpoint (https://mcp.stockmarketscan.com/mcp).
Is the StockMarketScan MCP server safe to use?
StockMarketScan scores 78 out of 100 on VerifyMCP. 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 StockMarketScan MCP server expose?
StockMarketScan exposes 20 tools: ping, list_screeners, get_screener_data, search_stocks_in_screeners, get_chart_patterns, and 15 more. Their descriptions and schemas cost roughly 3,469 tokens of context every time the server is loaded.
Does the StockMarketScan MCP server require authentication?
No. We connected to StockMarketScan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the StockMarketScan MCP server still maintained?
StockMarketScan is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the StockMarketScan MCP server?
VerifyMCP ran 13 checks on StockMarketScan, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.