MCP.Market

China Disclosures MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/china-disclosures·v0.2.1

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

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed China Disclosures yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

China Disclosures tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How China Disclosures compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 39% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
126 ms
faster than 78% of 30,031 servers

Release history: 7 versions in the registry since 2026-09-14, latest 2026-10-31, typically one every 5 days.

Install China Disclosures in Claude Code, Cursor or VS Code

claude mcp add --transport http china-disclosures https://gateway.pipeworx.io/china-disclosures/mcp
Add to Cursor

What the publisher says

From the China Disclosures repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/china-disclosures

Non-SEC Chinese biotech deals and HK/STAR IPO financing — licensing agreements and IPOs with no US-listed party, read straight out of the HKEX and CNINFO exchange disclosure feeds. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

licensing and collaboration deals disclosed by HKEX-listed companies, including deals with no US-listed party at all (e.g. a Chinese HKEX-listed biotech out-licensing to an Indian, Japanese, or European partner). Sourced from HKEXnews filings titled "License Agreement" or "Licensing Agreement".

  • hkexlicensingdeals(query?, since?, until?, limit?) — biotech/pharma

financing filings — the "GLOBAL OFFERING" prospectus and formal notice every company files with HKEX when it lists. Not biotech-specific; filter with query.

  • hkexipofilings(query?, since?, until?, limit?) — Hong Kong IPO / listing

search over CNINFO, the official disclosure feed for both Chinese A-share exchanges (Shenzhen + Shanghai, STAR Market included). Covers A-share-listed companies with zero HK/US nexus — the other half of the gap.

  • cninfodisclosuresearch(query, board?, since?, until?, limit?) — full-text

Why this exists, and why china-pharma / pharma-deals don't already cover it

chinalicensingdeals (china-pharma) and pharmalicensingdeals (pharma-deals) are both SEC 8-K based: they see a deal only if at least one party is US-listed. A China-to-China or China-to-Japan deal between two companies with no US listing is real, disclosed, and structurally invisible to either tool. Demand log, 2026-09-13 scouting pass: 3+ real asks for exactly that class of deal, plus HK/STAR biotech IPO financing.

Two more exchanges' own disclosure layers close the gap, both probed live 2026-09-13:

its own IPO under HKEX listing rules the same day, and HKEXnews' public title-search JSON endpoint (titleSearchServlet.do) serves those filings without a key. This is the same endpoint nmpadrugapprovals (china-pharma) already uses for NMPA approvals — same trick, different title term.

  • HKEX — any Hong Kong-listed company discloses a material licensing deal or

A-shares, STAR Market included. hisAnnouncement/query is a POST endpoint, no auth, plain browser UA — verified live returning 20,703 matches for searchkey=许可 (license/licence), dated as recent as the day of the probe.

  • CNINFO (cninfo.com.cn) — the official disclosure feed for SZSE + SSE

Traps

searchType=1 and title is set — verified across three different date windows (a 9-month range, a 1-month range, and a single day in 1990) on three different title terms ("License Agreement", "Licensing Agreement", "Global Offering"): identical result set every time. It is a rolling most-recent-titles window, not a date-filtered query. Both HKEX tools fetch the unbounded window and apply since/until themselves, client-side — a window before the reachable range returns found: false with an explicit hint naming the actual reachable dates, never a silently-empty "nothing that period".

  • HKEX titleSearchServlet.do ignores from/to entirely when

An initial probe of category=/plate=kcb for STAR Market returned HTTP 200 with the full unfiltered result set — a silent no-op, not an error. The real parameter, plate=shkcp, was found by watching the disclosure search page's OWN network request when its 科创板 (STAR Market) checkbox is selected in the browser — the same recipe china-exchange-data used for SZSE's report catalogs. Verified as a REAL filter, not another no-op: unfiltered searchkey=许可 returns totalAnnouncement: 20703; plate=shkcp returns 306, every one of them a 688xxx (STAR Market) code.

  • CNINFO's board/segment filter looks like it should be guessable and isn't.

Unfiltered vs. filtered, same search term, live 2026-09-13:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-10-03downgradeA → Bscore 73
  • 2026-09-19restoreB → Ascore 87

China Disclosures: common questions

Is China Disclosures MCP server safe?
Mostly: it is graded B (73/100). Read the China Disclosures safety report
How do I install China Disclosures?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does China Disclosures need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is China Disclosures maintained?
The last commit was 39 days ago (2026-09-25). The latest release is v0.2.1.
Is China Disclosures up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does China Disclosures compare with other MCP servers?
safety score 73/100 (higher than 39% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 126 ms (faster than 78% of 30,031 servers). Full comparison.

More from pipeworx-io →