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.SheldonZhuang/stock-sentinel

NPM · STOCK-SENTINEL-MCP

US stock attack/defense macro signals: 4-dimension framework, 26-year backtested. Research only.

Available components

0 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 73% of npm servers

Category Finance and Payments

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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1302 tokens (~162/item across 8 items; 8 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 Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

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

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/stock-sentinel-mcp@1.1.0

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 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,302 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
ask_company ~134

就一家 AI 产业链公司(MSFT/GOOGL/AMZN/META/NVDA/AMD/AVGO/TSM)提问,答案只依据其 SEC 申报原文与 XBRL 数据,每句附出处;程序逐句核对,核对不通过的句子不返回(unverified 计数)。不回答买卖建议、目标价或股价预测类问题。需要 API key(free 每日 5 次)。仅供研究参考,不构成投资建议。

NameTypeReqDescription
questionstringyes–
tickerstringyes–

No output schema declared.

No examples provided.

get_ai_chain ~104

获取AI产业链资金流向状态:六个环节(AI大模型→云厂商→AI芯片→存储/光模块→设备封装→电力)按30天相对SPY强弱的排名、当前市场隐含的卡点环节、以及泡沫监测三指标(模型调用量趋势/云厂商资本开支/半导体产出同比,按现金流向排序)。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_backtest_summary ~112

获取信号系统的历史回测核心结论:26年月度重放,覆盖6场危机(2000互联网泡沫/2008金融危机/2020新冠/2022加息熊/2025关税战/2026美伊战争)的捕获情况与8段大规模上涨期的捕获率,以及"仅全面防守离场"策略与买入持有的全期对比(年化/最大回撤)。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_current_signal ~452

获取美股当前进攻/防守信号。返回四档最终信号(attack进攻/neutral观望/reduce减仓观望/defense全面防守)、四个维度(AI供需/货币/财政/行政)各自的宽松/中性/收紧状态、以及全部参考指标(联邦基金利率、萨姆规则、联邦支出、WTI油价、EPU不确定性指数、美债收益率曲线、AI模型调用量等)。更新节奏:每日美东21:00生成完整快照;FOMC决议(美东14:00)与08:30月度宏观发布当天即时生效,indicators.rateSource=fed_statement 表示利率取自Fed官方声明(FRED序列尚未更新)。判定规则:进攻(非对称)=AI供需宽松且货币/财政/行政均不收紧(中性即可)且无锁且美债收益率曲线未处倒挂确认期(10y−3m近63个交易日中倒挂≥51天否决进攻准入)且信用利差未急剧走阔(Baa−10y利差90日走阔≥+60bp同样否决进攻准入)且实际利率未深度限制(政策利率−12M截尾PCE≥1.5%同样否决进攻准入);仅单维收紧=减仓观望(语义:停止加仓提高警觉,非必须减存量仓位);双维以上收紧或衰退锁激活=全面防守(例外:纯货币+财政共振降为减仓;上升趋势中树驱动与萨姆锁驱动的防守降级为减仓,应对式调整锁不受趋势否决;趋势地板:跌破10月SMA时最终档位至少减仓观望)。仅供研究参考,不构成投资建议。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_daily_report ~48

获取AI生成的每日信号解读(中英双语):今日档位、由哪些维度和数据驱动、距离进攻/防守的条件差距。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_research_note ~240

获取 AI 产业链公司(MSFT/GOOGL/AMZN/META/NVDA/AMD/AVGO/TSM)某财季的结构化研究笔记:关键数字(XBRL,本季/上季/去年同期/环比/同比)、要点、对照管理层指引(是否达成由程序计算)、变化、风险点、未披露项。每条陈述附出处(XBRL 字段或 SEC 原文链接+字符区间+逐字引文);未通过程序核对的陈述标 needs_review。quarter 用财年口径如 FY2026Q4(MSFT 财年 6 月结束、NVDA 1 月结束),省略取最新。仅供研究参考,不构成投资建议,不提供买卖建议或股价预测。

NameTypeReqDescription
quarterstring–财年财季,如 FY2026Q4;省略取最新
tickerstringyesMSFT/GOOGL/AMZN/META/NVDA/AMD/AVGO/TSM

No output schema declared.

No examples provided.

get_signal_history ~67

获取信号历史存档(公开可验证的 track record):每日的最终档位与四维状态,按日期倒序。可用于回看信号在近期市场事件中的表现。

NameTypeReqDescription
limitinteger–返回天数,默认90,最大365

No output schema declared.

No examples provided.

get_stock_percentile ~145

查询个股或ETF:当前价格在历史区间中的百分位(≥80%高位/≤20%低位)、真实市盈率P/E与市销率P/S(SEC EDGAR财报口径)。支持指数别名:US10Y(10年美债收益率)、VIX、SPX、NDX。

NameTypeReqDescription
endDatestring–区间终点 YYYY-MM-DD,默认今天
startDatestring–区间起点 YYYY-MM-DD,默认3年前
symbolstringyes股票代码,如 NVDA、AAPL、QQQ、US10Y

No output schema declared.

No examples provided.

Install

How do I install the io.github.SheldonZhuang/stock-sentinel MCP server?

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

npm · stock-sentinel-mcp

# add to Claude Code
claude mcp add sheldonzhuang-stock-sentinel -- npx -y stock-sentinel-mcp
Common questions

What is the io.github.SheldonZhuang/stock-sentinel MCP server?

io.github.SheldonZhuang/stock-sentinel is an MCP server listed in the public MCP registry as io.github.SheldonZhuang/stock-sentinel. US stock attack/defense macro signals: 4-dimension framework, 26-year backtested. Research only. This page covers its npm package (stock-sentinel-mcp).

Is the io.github.SheldonZhuang/stock-sentinel MCP server safe to use?

io.github.SheldonZhuang/stock-sentinel scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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.SheldonZhuang/stock-sentinel MCP server expose?

io.github.SheldonZhuang/stock-sentinel exposes 8 tools: get_current_signal, get_signal_history, get_ai_chain, get_stock_percentile, get_backtest_summary, and 3 more. Their descriptions and schemas cost roughly 1,302 tokens of context every time the server is loaded.

Is the io.github.SheldonZhuang/stock-sentinel MCP server still maintained?

io.github.SheldonZhuang/stock-sentinel 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 licence is the io.github.SheldonZhuang/stock-sentinel MCP server under?

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

What did VerifyMCP test on the io.github.SheldonZhuang/stock-sentinel MCP server?

VerifyMCP ran 16 checks on io.github.SheldonZhuang/stock-sentinel, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.