cn-safe-penalties
by pipeworx-io
README.md
# @pipeworx/cn-safe-penalties
Has China's State Administration of Foreign Exchange (国家外汇管理局) publicly named this firm in a foreign-exchange violation case: for what conduct, under which article, and with what fine or confiscation? Rows are the Administration's published notices of foreign-exchange violation cases (外汇违规案例的通报), read from its release list. Firms and banks only.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1964+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `cn_safe_violation_notices_search(query?, page?, limit?)` -- one call reads one page of the Administration's newest-first release list (about 20 releases per page, 64 pages), picks the violation-case notices on it and reads up to `limit` (1-3) of them. Each firm case gives the case title, the entity, the conduct as the Administration describes it, the penalty text and the link to the official notice. `query` is Chinese text matched only within the cases of the notices read (the publisher offers no keyword search); `page` moves back in time. Also returns `searched` (page, pages_total, the dates the page covers, how many violation notices the page holds and how many were read, titles not read), `individual_cases_omitted`, `unclassified_cases_omitted`, `person_sentences_omitted`, `unread_notices` and `data_as_of`.
- `cn_safe_violation_notice_get(notice_url, query?)` -- reads one notice in full (firm cases only), from a `notice_url` returned by the search.
## Auth
Keyless.
## Data sources
- State Administration of Foreign Exchange (国家外汇管理局), notices of foreign-exchange violation cases (外汇违规案例的通报), published several times a year since 2018. Read from the publisher on each call; nothing is stored.
## Individuals are not returned
The notices mix companies, banks and natural persons. A case against a natural person is left out and counted (`individual_cases_omitted`). A case that cannot be classified as a firm or a person is left out and counted (`unclassified_cases_omitted`). Sentences inside a firm case that name a person are dropped and counted (`person_sentences_omitted`). Every response carries a `note` saying so; the tests prove that a person's name never appears in a response.
## Behaviour worth knowing
- Violation notices are a few a year among many releases, so the newest page often holds none (`empty_reason: no_violation_notice_on_this_page`). Walk `page`; the response names the dates each page covers. No match is never evidence that a firm was not penalised.
- A notice that cannot be read is counted in `unread_notices` and reported as `empty_reason: unread`, never as an empty result. A changed page layout or an error page is an `upstream_down` error.
- These notices are a selection of typical cases chosen by the Administration, not a complete register of penalties; the Administration's regional branches publish their own decisions elsewhere.
- Text is the Administration's own wording, in simplified Chinese.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"cn-safe-penalties": {
"url": "https://gateway.pipeworx.io/cn-safe-penalties/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/cn-safe-penalties/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:
```json
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
```
Both URLs reach the same gateway and the same 1964+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.
## No MCP client? Call it over HTTP
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/cn_safe_violation_notices_search \
-H 'Content-Type: application/json' \
-d '{"page":20,"limit":1}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/cn_safe_violation_notices_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-cn-safe-penalties` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/cn-safe-penalties/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"cn-safe-penalties": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-cn-safe-penalties"]
}
}
}
```
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.
## Using with ask_pipeworx
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:
```
ask_pipeworx({ question: "your question about Cn Safe Penalties data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues