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 Commerce

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

China's Ministry of Commerce (MOFCOM) 商务数据中心 (data.mofcom.gov.cn) — monthly national series for…

+18 this week 72 Trust /100

Last scanned (10 hours ago)

Scores higher than 44% 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 & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1097 tokens (~219/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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.

  • 22 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.

  • 20 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.

  • 19 Nov 26 +1
    • Stability: unverified → 0.13 ▲ functional
  • 16 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Nov 26 54

    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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-china-commerce@0.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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,044 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
mofcom_fdi_utilised ~245

Utilised inbound foreign direct investment into China (吸收外商直接投资) and newly established FDI enterprises — monthly YEAR-TO-DATE CUMULATIVE figures, each with year-over-year %. Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January. The monetary amount (USD 100M) stopped being published through this feed around mid-2023 — recent rows carry the enterprise COUNT only, with the dollar figure null. Answers "how much FDI is China attracting", "new foreign-invested enterprises in China this year".

NameTypeReqDescription
end_periodstring–Latest period to include, as YYYYMM or YYYY-MM. Omit for the most recent available month.
limitnumber–Max rows to return, newest first (default 24, max 500). Ignored range still comes from start_period/end_period — this only caps how many of those rows come back.
start_periodstring–Earliest period to include, as YYYYMM or YYYY-MM (e.g. "2024-01" or "202401"). Omit for full history.

No output schema declared.

No examples provided.

mofcom_labor_cooperation ~246

China's overseas labour dispatch (对外劳务合作) — monthly YEAR-TO-DATE CUMULATIVE count (in 10,000-person units) of Chinese workers dispatched abroad, split by whether they went out under contracted-engineering projects or under standalone labour-cooperation contracts, plus the year-over-year change (an ABSOLUTE change in 10,000-person units, not a percent). Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January. Answers "how many Chinese workers are sent abroad", "China overseas labour export trend".

NameTypeReqDescription
end_periodstring–Latest period to include, as YYYYMM or YYYY-MM. Omit for the most recent available month.
limitnumber–Max rows to return, newest first (default 24, max 500). Ignored range still comes from start_period/end_period — this only caps how many of those rows come back.
start_periodstring–Earliest period to include, as YYYYMM or YYYY-MM (e.g. "2024-01" or "202401"). Omit for full history.

No output schema declared.

No examples provided.

mofcom_odi ~269

China's non-financial outward direct investment (对外直接投资, ODI) — monthly YEAR-TO-DATE CUMULATIVE amount in USD 100M, number of enterprises investing abroad, and the count of countries/regions reached, each with year-over-year %. Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January (累计 = Jan-through-month, not a standalone monthly flow) — the response's `note` field restates this. No per-country breakdown is available (the country count is a COUNT, not a split by destination). Answers "China's outward FDI this year", "how many Chinese enterprises are investing abroad", "China ODI growth rate".

NameTypeReqDescription
end_periodstring–Latest period to include, as YYYYMM or YYYY-MM. Omit for the most recent available month.
limitnumber–Max rows to return, newest first (default 24, max 500). Ignored range still comes from start_period/end_period — this only caps how many of those rows come back.
start_periodstring–Earliest period to include, as YYYYMM or YYYY-MM (e.g. "2024-01" or "202401"). Omit for full history.

No output schema declared.

No examples provided.

mofcom_overseas_contracting ~213

China's overseas contracted engineering projects (对外承包工程) — monthly YEAR-TO-DATE CUMULATIVE value of newly signed contracts and completed turnover, both in USD 100M, each with year-over-year %. Sourced live from MOFCOM's (商务部) data centre, keyless. Values reset down every January. Answers "value of China's overseas construction/engineering contracts", "Chinese contractors' overseas project turnover".

NameTypeReqDescription
end_periodstring–Latest period to include, as YYYYMM or YYYY-MM. Omit for the most recent available month.
limitnumber–Max rows to return, newest first (default 24, max 500). Ignored range still comes from start_period/end_period — this only caps how many of those rows come back.
start_periodstring–Earliest period to include, as YYYYMM or YYYY-MM (e.g. "2024-01" or "202401"). Omit for full history.

No output schema declared.

No examples provided.

mofcom_series_list ~71

Lists the four MOFCOM data-centre series this pack covers (ODI, overseas contracting, labour cooperation, utilised FDI) with their Chinese/English names, units, and the live earliest/latest period each currently has — a cheap discovery call before picking which of the other four tools to use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the China Commerce MCP server?

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

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

What is the China Commerce MCP server?

China Commerce is an MCP server listed in the public MCP registry as io.github.pipeworx-io/china-commerce. China's Ministry of Commerce (MOFCOM) 商务数据中心 (data.mofcom.gov.cn), monthly national series for… This page covers its npm package (@pipeworx/mcp-china-commerce).

Is the China Commerce MCP server safe to use?

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

China Commerce exposes 5 tools: mofcom_odi, mofcom_overseas_contracting, mofcom_labor_cooperation, mofcom_fdi_utilised, mofcom_series_list. Their descriptions and schemas cost roughly 1,044 tokens of context every time the server is loaded.

Is the China Commerce MCP server still maintained?

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

China Commerce 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 Commerce MCP server?

VerifyMCP ran 16 checks on China Commerce, 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.