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.

China Disclosures

NPM · @PIPEWORX/MCP-CHINA-DISCLOSURES · 2 COMPONENTS

China Disclosures MCP — non-SEC Chinese biotech deals and HK/STAR IPO financing, read straight out…

+3 this week 81 Trust /100

Last scanned (1 hour ago)

Scores higher than 68% 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 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-disclosures). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1318 tokens (~329/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 Management23
  • Stability observed for 7 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
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.

  • 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 +1
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 +1

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

  • 29 Oct 26 78

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-china-disclosures@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-disclosures
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-china-disclosures/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606762851
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d684983e1ad37ba054414a878b30f9177da8f678d2b76a56c628cbd24757889495400ec1821798ccddcfec22bbf3915edd437def6fb969e1f057a2730

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,263 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
cn_uscc_validate ~281

Offline validator and decoder for China's 18-character Unified Social Credit Code (统一社会信用代码, GB 32100-2015) -- the single identifier every registered Chinese organization (company, social organization, government institution) carries. Checks the format (length, allowed 31-character set, and the GB 32100-2015 check-digit algorithm) and, when valid, decodes the registration authority (e.g. Market Regulation for an ordinary company), the entity type, and the province from the 6-digit administrative-division segment. No network call -- this is a pure offline algorithm plus small public lookup tables (GB/T 2260 province codes), so it works for any syntactically plausible code, including ones that do not exist. Answers "is this a valid Chinese company code", "decode this unified social credit code", "check digit for 9111000012345678AU", "which province does this USCC belong to". IMPORTANT: this validates FORMAT ONLY -- a format-valid code is not proof a real company holds it; confirming existence requires a live registry lookup this tool does not perform (see format_only_note in every response).

NameTypeReqDescription
codestringyesThe 18-character Unified Social Credit Code to validate, e.g. "9111000012345678AU". Case-insensitive; surrounding whitespace is trimmed.

No output schema declared.

No examples provided.

cninfo_disclosure_search ~378

Full-text search over CNINFO (cninfo.com.cn), the official disclosure feed for BOTH Chinese A-share exchanges — Shenzhen (SZSE) and Shanghai (SSE), STAR Market (科创板) included. Covers A-share-listed companies with zero HK or US nexus — the deals and IPOs invisible to every SEC- or HKEX-based tool in this catalog (a China-to-China licensing deal, or a STAR Market IPO prospectus). Answers "A股许可协议公告" (A-share licensing announcements), "STAR Market IPO prospectus filings", "科创板 招股说明书". Search terms must be Chinese (e.g. "许可" for licensing/approval disclosures, "招股说明书" for IPO prospectuses) — do not translate an English query and search that. Optionally filter to one verified board segment (`board`). Returns company, stock code, title, date and PDF link, plus the true total match count.

NameTypeReqDescription
boardstring–Restrict to one verified board segment: "star" = STAR Market (科创板, SSE, all 688xxx codes) or "chinext" = ChiNext (创业板, SZSE). Omit to search all SZSE+SSE boards.
limitnumber–Maximum disclosures to return, 1-40 (default 15).
querystringyesChinese-language search term, e.g. "许可" (license/licensing) or "招股说明书" (IPO prospectus). Required.
sincestring–Earliest disclosure date, YYYY-MM-DD. Omitted, no lower bound (server-side date filter, genuinely narrows results).
untilstring–Latest disclosure date, YYYY-MM-DD. Defaults to today. Only applied when `since` is also set.

No output schema declared.

No examples provided.

hkex_ipo_filings ~296

Hong Kong IPO / listing financing filings — the Global Offering prospectus and formal notice every company files with HKEX when it goes public or completes a placement. Answers "recent HK IPOs", "HKEX biotech IPO financing", "which companies just listed on the Hong Kong Stock Exchange", "STAR/HK biotech listing documents". Sourced from HKEXnews disclosure filings titled "GLOBAL OFFERING" — covers every industry, not biotech-specific, so filter with `query` (a company name) to find a particular listing. Returns the company, stock code, document category (Listing Documents = the prospectus PDF, or Announcements and Notices = the formal notice for the same event), filing date and PDF link. HKEX Main Board / GEM only — an A-share STAR Market (科创板) IPO is a different exchange, see cninfo_disclosure_search.

NameTypeReqDescription
limitnumber–Maximum filings to return, 1-40 (default 15).
querystring–Filter to filings whose company name contains this text (e.g. "BIO", "PHARMA", or a specific company).
sincestring–Earliest filing date, YYYY-MM-DD. Defaults to 90 days ago. Only the current rolling HKEXnews window is reachable — see source_note in the response.
untilstring–Latest filing date, YYYY-MM-DD. Defaults to today.

No output schema declared.

No examples provided.

hkex_licensing_deals ~308

Biotech/pharma licensing and collaboration deals disclosed by Hong Kong Exchange (HKEX)-listed companies — covers deals with NO US-listed party at all (e.g. a Chinese HKEX-listed biotech out-licensing a drug to an Indian, Japanese or European partner), which SEC-filing-based tools (china_licensing_deals, pharma_licensing_deals) structurally cannot see. Answers "China-to-Japan biotech licensing deals", "recent Asia pharma out-licensing deals not filed with the SEC", "HKEX biotech collaboration agreements". Sourced from HKEXnews disclosure filings whose title contains "License Agreement" or "Licensing Agreement". Returns the company, stock code, headline, filing category and date, and the filing PDF. Coverage requires the Chinese/Asian party to be HKEX-listed — a private-to-private deal with no HK, US or A-share party is invisible to every tool in this catalog.

NameTypeReqDescription
limitnumber–Maximum deals to return, 1-40 (default 15).
querystring–Filter to filings whose headline or company name contains this text (a drug code, company name, or partner name).
sincestring–Earliest filing date, YYYY-MM-DD. Defaults to 90 days ago. Only the current rolling HKEXnews window is reachable — see source_note in the response.
untilstring–Latest filing date, YYYY-MM-DD. Defaults to today.

No output schema declared.

No examples provided.

Install

How do I install the China Disclosures MCP server?

China Disclosures runs locally as an npm package, launched with npx -y @pipeworx/mcp-china-disclosures. 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-disclosures

# add to Claude Code
claude mcp add pipeworx-io-china-disclosures -- npx -y @pipeworx/mcp-china-disclosures
Common questions

What is the China Disclosures MCP server?

China Disclosures is an MCP server listed in the public MCP registry as io.github.pipeworx-io/china-disclosures. China Disclosures MCP, non-SEC Chinese biotech deals and HK/STAR IPO financing, read straight out… This page covers its npm package (@pipeworx/mcp-china-disclosures).

Is the China Disclosures MCP server safe to use?

China Disclosures scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Disclosures MCP server expose?

China Disclosures exposes 4 tools: hkex_licensing_deals, hkex_ipo_filings, cninfo_disclosure_search, cn_uscc_validate. Their descriptions and schemas cost roughly 1,263 tokens of context every time the server is loaded.

Is the China Disclosures MCP server still maintained?

China Disclosures is still listed as active in the MCP registry. We last reached this channel on 5 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 Disclosures MCP server under?

China Disclosures declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.