Stock Screener
PYPI · STOCKSCREEN-MCP
Daily stock screens, RS ratings, market breadth and group rankings for 12 markets. No API keys.
Available components
Last scanned (22 hours ago)
Scores higher than 92% of PyPI servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to xang1234/stock-screener). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1071 tokens (~178/item across 6 items; 6 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 Management70
- Stability observed for 21 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed pypi/stockscreen-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | xang1234/stock-screener |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/xang1234/stock-screener/.github/workflows/stockscreen-mcp-release.yml@refs/tags/stockscreen-mcp-v0.1.1 |
| Rekor log index | 3274176241 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:a20075ce1619ccefd2c365068044fa0c193ab3f17dfde4c90437eb41e0cc181f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_stock ~100
Everything the daily scan knows about one stock: RS ratings, stage, scores, growth, group rank, setup/pattern fields, and which preset screens it currently passes.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Market code, e.g. US, HK, JP, IN, DE. See list_markets. |
| symbol | string | yes | Ticker as listed in that market, e.g. NVDA, 0700.HK, 7203.T. |
Structured output declared, but exposes no named fields.
No examples provided.
group_rankings ~196
Rank a market's IBD-style industry groups by their stocks' relative strength (1 = strongest), with 1W/1M/3M/6M rank changes and this week's biggest movers. Use it to find leading or improving industries. Pass `group` (full name, or any part of it that matches only one group) for that group's rank history and its stocks, strongest RS first. For a quick top-5 alongside breadth, market_overview is enough; to filter stocks by group rank, use run_screen with ibd_group_rank. Rankings are end-of-day and update once a day.
| Name | Type | Req | Description |
|---|---|---|---|
| group | – | – | Industry group name for its detail and constituents. |
| limit | integer | – | Groups to return, or with `group`, constituent stocks to return. |
| market | string | – | Market code, e.g. US, HK, JP, IN, DE. See list_markets. |
Structured output declared, but exposes no named fields.
No examples provided.
list_markets ~222
List the markets that have published data, so you know which market codes the other tools accept and how fresh each one is. Call this first when the user names a country or exchange, or asks how current the data is. For one market's health, breadth and leading groups, use market_overview instead. Each market returns its code (pass it as `market` to the other tools), name, as_of_date (the trading day the data covers), status ("current"; "late" if it is behind its latest completed session or its next update is over a day overdue; or "unknown"), and features: which of "scan" (run_screen, get_stock, list_screens), "breadth" (market_overview breadth) and "groups" (group_rankings) are published for it. unavailable_markets lists markets that failed this publish. Takes no arguments. Results are cached for up to 10 minutes; markets are published after their close by two scheduled runs, one for Asia and one for US/Europe.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_screens ~70
Preset screens (Minervini, CANSLIM, VCP, chart patterns, momentum...) with their exact rules. Pass a screen's id to run_screen.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Market code, e.g. US, HK, JP, IN, DE. See list_markets. |
Structured output declared, but exposes no named fields.
No examples provided.
market_overview ~95
Market health in one call: exposure score and stance (distribution days, follow-through day, trend), StockBee-style breadth (4% movers, 5/10-day ratios, T2108, 52-week highs/lows), key index/asset moves, and the strongest industry groups.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Market code, e.g. US, HK, JP, IN, DE. See list_markets. |
Structured output declared, but exposes no named fields.
No examples provided.
run_screen ~167
Run a preset screen and/or custom filters over a market's full daily scan (every listed stock). A preset matches exactly the stocks the project's website shows for it. Filters are combined with AND, including with the preset.
| Name | Type | Req | Description |
|---|---|---|---|
| descending | boolean | – | Direction for sort_by; ignored without sort_by. |
| filters | – | – | Extra conditions, all of which must hold. |
| limit | integer | – | Rows to return; total_matches counts all. |
| market | string | – | Market code, e.g. US, HK, JP, IN, DE. See list_markets. |
| screen | – | – | Preset id from list_screens, e.g. minervini, canslim, vcp. |
| sort_by | – | – | Field to sort by; defaults to the screen's own sort. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Stock Screener MCP server?
Stock Screener runs locally as a PyPI package, launched with uvx stockscreen-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · stockscreen-mcp
claude mcp add xang1234-stockscreen-mcp -- uvx stockscreen-mcp
What is the Stock Screener MCP server?
Stock Screener is an MCP server listed in the public MCP registry as io.github.xang1234/stockscreen-mcp. Daily stock screens, RS ratings, market breadth and group rankings for 12 markets. No API keys. This page covers its PyPI package (stockscreen-mcp).
Is the Stock Screener MCP server safe to use?
Stock Screener scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Stock Screener MCP server expose?
Stock Screener exposes 6 tools: list_markets, list_screens, run_screen, get_stock, market_overview, group_rankings. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.
Is the Stock Screener MCP server still maintained?
Stock Screener is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Stock Screener MCP server under?
Stock Screener declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.