The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the China Safe listing page.
China's official reserve assets, balance of payments, and external debt — 外汇储备 (FX reserves), 国际收支 (balance of payments), 外债 (external debt) — parsed from the English-language data pages of SAFE, the State Administration of Foreign Exchange (国家外汇管理局).
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
china_fx_reserves({months}) — monthly official reserve assets: headline
FX reserves (外汇储备), IMF reserve position, SDR holdings, gold (value +
ounces), other reserve assets, and the total. MONTHLY, published roughly
one week after month-end. Verified 2026-09-07: August 2026 was the newest
month — FX reserves USD 3,438.325bn, total official reserve assets
USD 3,854.885bn — published on 2026-09-07.china_balance_of_payments({quarters, currency}) — quarterly BOP summary:
current account (goods, services, primary/secondary income), capital and
financial account (incl. the reserve-assets change), and net errors and
omissions. currency is usd (default), rmb, or sdr. QUARTERLY, with
roughly a 3-month lag after quarter-end — this is the standard BPM6 release
cadence, not a stale site. Verified 2026-09-07: latest quarter was 2026Q1,
published 2026-06-26.china_external_debt({quarters}) — quarterly gross external debt position
(外债) since 2014Q4: total, by original-contract maturity (short/long-term),
and by institutional sector (general government, central bank, other
depository corporations, other sectors, direct-investment intercompany
lending). Same ~3-month quarterly lag as BOP. Verified 2026-09-07: latest
quarter was 2026Q1, published 2026-06-26.china_safe_releases({limit}) — the REAL publish dates behind the other
three tools, read from each source page's own PubDate metadata and its
attached file's upload timestamp, not the page's permalink. Use this before
citing a number from the other tools if freshness matters to the caller.Keyless.
/en/2021/0203/2045.html, a 2021-dated path, and was still updating live
data as of 2026-09-07. Trust the article page's own
<meta name="PubDate"> and the date embedded in the attached file's own
path (/en/file/file/20260907/....xlsx), never the permalink.src/xlsx.ts, ported from the
ema-medicines pack's reader) — a Worker can't carry a full xlsx library
for three files.<a href="https://github.com/pipeworx-io/mcp-china-safe/blob/HEAD/...">xlsx</a>); BOP/external-debt pages put
the full report title as the anchor text and the filename only in a
title="..." attribute. Match on the .xlsx href extension, not the
anchor text.gold_million_oz directly.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/china-safe/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/china_fx_reserves. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT