China Exchange Data
NPM · @PIPEWORX/MCP-CHINA-EXCHANGE-DATA · 2 COMPONENTS
China Exchange Data MCP (SZSE + SSE). Keyless.
Available components
Last scanned (13 hours ago)
Scores higher than 74% of npm 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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-china-exchange-data). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1288 tokens (~322/item across 4 items; 4 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 Management30
- Stability observed for 9 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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 (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 →
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.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 +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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
First indexed and scored.
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 7 Nov 2026 · Analysed npm/@pipeworx/mcp-china-exchange-data@0.2.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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-china-exchange-data |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-china-exchange-data/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606766378 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:557919e0c547a4a033cb17a036d362cc85093fd741b4c914d8ea80b956e7c9bd3fe0ff6e6ec582eed30acc23b73ff7d17bb914d1fa5883faedecdbb29 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
ashares_bulletins ~263
上交所上市公司公告 — SSE-listed company disclosure bulletins (公告) by 6-digit code: title, type (半年报/年报/董事会/股东会/回购/关联交易 etc.), date, and the PDF URL on sse.com.cn. Answers "600519最新公告", "贵州茅台公司公告", "SSE company bulletins since 2026-01-01", "annual report / 年报 filings for a code". SZSE-listed codes (0/3-prefixed) are not covered — this endpoint is SSE-only. Source: SSE queryCompanyBulletinNew (keyless).
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 6-digit SSE code, e.g. "600519" (贵州茅台). |
| limit | number | – | Max bulletins to return, 1-100 (default 20, newest first). The response always reports the true total on file. |
| since | string | – | Only return bulletins on or after this date, YYYY-MM-DD (default: no lower bound — most recent first). |
| type | string | – | Filter by bulletin type substring, e.g. "年报" or "股东会" (default: all types). |
No output schema declared.
No examples provided.
ashares_index_bars ~421
上证/深证指数日线周线年线 — Daily, weekly, or annual OHLC + volume + turnover bars for a major China A-share index: 上证指数 Shanghai Composite (000001), 上证50 (000016), 沪深300 CSI 300 (000300), 科创50 STAR50 (000688) from SSE; 深证成指 Shenzhen Component (399001), 创业板指 ChiNext (399006) from SZSE. Weekly history goes back up to 6 years (312 bars); `years` returns one bar per calendar year (close + year-over-year pct change) for multi-year questions like "5 years of annual closes for CSI 300". Answers "上证指数000001最近10个交易日OHLC", "Shanghai Composite last 10 days", "深证成指周线", "ChiNext index history", "CSI 300 annual close 2020-2025". Source: SSE yunhq public quote system (000xxx/999xxx indices) + SZSE ssjjhq history API (399xxx indices), both keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Number of daily bars to return, 1-250 (default 10). Ignored if weeks or years is set. |
| index | string | – | Index code: 000001 (上证指数), 000016 (上证50), 000300 (沪深300), 000688 (科创50), 399001 (深证成指), 399006 (创业板指). Default 000001. |
| weeks | number | – | Number of weekly bars to return, 1-312 (up to ~6 years). Overrides days when set; ignored if years is set. |
| years | number | – | Number of annual bars to return, 1-40 — one bar per calendar year with close and year-over-year pct_change. Overrides weeks and days when set. E.g. years:6 for 2020-2025 inclusive. |
No output schema declared.
No examples provided.
ashares_market_bars ~273
沪市全市场行情 — Full-market latest-session board snapshot for SSE-listed A-shares (~2,358 stocks): code, name, last price, change %, volume, turnover amount (成交额). Built for running screens (momentum vs index, top movers) without querying each stock individually. This is the LATEST available trading session only (a live board snapshot, not a historical-date archive) — SZSE does not expose an equivalent single-call full-market bulk endpoint (its per-stock snapshot report needs one call per code), so this tool covers the Shanghai exchange only; asking for a past date returns the latest session with a note rather than silently substituting data. Answers 'A股全市场行情', 'SSE full board today', 'screen all Shanghai A-shares by turnover'. Source: SSE yunhq public quote list (keyless).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Requested date, YYYY-MM-DD. Informational only — the tool always returns the latest available SSE session and reports whether it matches this date. |
| limit | number | – | Max rows to return, 1-2500 (default 500). The response always reports the true total row count on the board. |
| sort | string | – | Sort rows by turnover amount (default), change %, or volume, descending. |
No output schema declared.
No examples provided.
ashares_sector_flows ~274
深交所 A股行业板块统计 — SZSE-official per-industry (行业) turnover ranking for the Chinese A-share market: turnover amount (成交金额/亿元), share volume, company count, total and float market cap, and weighted-average P/E, one row per SZSE industry classification (A 农林牧渔 … T 综合 etc.), for a given trading day. This is the exchange's own published turnover-by-industry statistic — NOT the vendor-computed "主力资金净流入" (large-order net capital inflow) metric that East Money / 同花顺-style trackers publish; neither SZSE nor SSE discloses that classification publicly, so it is not offered here. Answers "今天A股行业板块成交额排名", "which sectors traded the most today", "SZSE industry turnover ranking". Sorted by turnover amount descending. Source: SZSE ShowReport CATALOGID=1804_gptj_merge_after (keyless).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Trading day as YYYY-MM-DD (default: today). SZSE returns the most recently published session if the exact date has no data yet. |
| top | number | – | How many industries to return, 1-50 (default 10, all if omitted total is under that). |
No output schema declared.
No examples provided.
How do I install the China Exchange Data MCP server?
China Exchange Data runs locally as an npm package, launched with npx -y @pipeworx/mcp-china-exchange-data. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-china-exchange-data
claude mcp add pipeworx-io-china-exchange-data -- npx -y @pipeworx/mcp-china-exchange-data
What is the China Exchange Data MCP server?
China Exchange Data is an MCP server listed in the public MCP registry as io.github.pipeworx-io/china-exchange-data. China Exchange Data MCP (SZSE + SSE). Keyless. This page covers its npm package (@pipeworx/mcp-china-exchange-data).
Is the China Exchange Data MCP server safe to use?
China Exchange Data scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. 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 China Exchange Data MCP server expose?
China Exchange Data exposes 4 tools: ashares_sector_flows, ashares_index_bars, ashares_market_bars, ashares_bulletins. Their descriptions and schemas cost roughly 1,231 tokens of context every time the server is loaded.
Is the China Exchange Data MCP server still maintained?
China Exchange Data is still listed as active in the MCP registry. We last reached this channel on 7 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 China Exchange Data MCP server under?
China Exchange Data 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 China Exchange Data MCP server?
VerifyMCP ran 16 checks on China Exchange Data, 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.