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.

Cn Futures

NPM · @PIPEWORX/MCP-CN-FUTURES · 2 COMPONENTS

China Futures MCP. Keyless.

+18 this week 72 Trust /100

Last scanned (23 minutes 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 Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 619 tokens (~206/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +2
    • 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-cn-futures@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 · 3 exposed · ~565 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_futures_daily ~264

Daily settlement report for one China commodity futures product on one trading day: every contract's open, high, low, close, settlement, prior settlement, volume (lots), open interest and turnover, plus a main contract (highest open interest). Covers SHFE (rebar rb, gold au, silver ag, copper cu...), INE (crude sc, rubber nr...), ZCE (cotton CF, sugar SR, apples AP...) and GFEX (lithium carbonate lc, industrial silicon si...). A listed-but-dormant product (e.g. ZCE wheat WH) returns status "no_listed_activity" with an explanation, not an empty list. DCE (Dalian) is not available. Prices in CNY. Defaults to the latest published trading day.

NameTypeReqDescription
datestring–Trading day, YYYY-MM-DD or YYYYMMDD. Omit for the latest published day. Weekends and holidays have no file.
exchangestring–Optional. Inferred from the product code when omitted.
productstringyesExchange product code, case-insensitive: "rb" rebar, "au" gold, "ag" silver, "CF" cotton, "WH" wheat, "lc" lithium carbonate

No output schema declared.

No examples provided.

cn_futures_products ~123

List every product in one China futures exchange's daily report (SHFE, INE, ZCE or GFEX) for a trading day, ranked by open interest: contract count, total volume, total open interest, main contract and its settlement, and whether the product has any trading activity. Use to discover product codes before cn_futures_daily. Defaults to the latest published trading day.

NameTypeReqDescription
datestring–Trading day, YYYY-MM-DD or YYYYMMDD. Omit for the latest published day.
exchangestringyesExchange to list

No output schema declared.

No examples provided.

cn_futures_warehouse_stocks ~178

Shanghai Futures Exchange daily warehouse-receipt (warrant) stocks: gold and silver in kilograms, base metals, rebar, hot-rolled coil and other products in tonnes, with the day-over-day change and the per-warehouse breakdown. This is stock made into warrants for delivery, not total physical inventory. Pass a product code or name (au, ag, rb, copper...) for the full breakdown, or omit it for a one-line total per product. Defaults to the latest published report.

NameTypeReqDescription
datestring–Report day, YYYY-MM-DD or YYYYMMDD. Omit for the latest published report.
productstring–Product code or name: "au" or "gold", "ag" or "silver", "rb", "cu"... Omit for every product's total.

No output schema declared.

No examples provided.

Install

How do I install the Cn Futures MCP server?

Cn Futures runs locally as an npm package, launched with npx -y @pipeworx/mcp-cn-futures. 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-cn-futures

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

What is the Cn Futures MCP server?

Cn Futures is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cn-futures. China Futures MCP. Keyless. This page covers its npm package (@pipeworx/mcp-cn-futures).

Is the Cn Futures MCP server safe to use?

Cn Futures 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 Cn Futures MCP server expose?

Cn Futures exposes 3 tools: cn_futures_daily, cn_futures_products, cn_futures_warehouse_stocks. Their descriptions and schemas cost roughly 565 tokens of context every time the server is loaded.

Is the Cn Futures MCP server still maintained?

Cn Futures 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 Cn Futures MCP server under?

Cn Futures 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 Cn Futures MCP server?

VerifyMCP ran 16 checks on Cn Futures, 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.