cn-csrc-actions
by pipeworx-io
README.md
# @pipeworx/cn-csrc-actions
Has the China Securities Regulatory Commission (中国证监会) penalised this firm: which decision, when, for what conduct, and what penalty? Rows are the Commission's published administrative penalty decisions (行政处罚决定书), newest first. Firms 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_csrc_enforcement_search(query?, date_from?, date_to?, type?, page?, limit?)` -- one request reads one page of 20 notices (newest first). Each firm notice gives the document number, publication date, the firm(s) penalised, the conduct the Commission investigated as it states it, the decision text for that firm (fines, confiscation, warnings, corrective orders) and the link to the official notice. `query` is Chinese text matched against the notices on the page read (the publisher offers no keyword search); `date_from` narrows the list on the publisher's side; `date_to` trims the page; `page` moves through the list; `type` is a word that must appear in the firm's decision (罚款, 警告, 没收). Also returns `searched` (page, pages_total, the dates the page covers), `skipped_possible_individuals`, `omitted_individual_only_notices`, `unread_notices` and `data_as_of`.
## Auth
Keyless.
## Data sources
- China Securities Regulatory Commission (中国证监会), administrative penalty decisions (行政处罚决定书), about 2,000 decisions since 2003. Read from the publisher on each call; nothing is stored.
## Individuals are not returned
The Commission mostly penalises people. A notice whose parties are all natural persons is left out (counted in `omitted_individual_only_notices`). A notice naming a firm and people returns the firm and the decision lines about the firm; the people's names, roles and decision lines are dropped (counted in `individuals_omitted`). A party the pack cannot classify as a firm or a person is left out and counted in `skipped_possible_individuals`. A notice whose party block cannot be read is counted in `unread_notices`, never dropped silently. Every response carries a `note` saying so; the tests prove that a person's name never appears in a response.
## Behaviour worth knowing
- A search covers one page. No match means no match on that page and period (`empty_reason: no_match_on_this_page`, with the page, the page count and the dates covered); it is not evidence that a firm was never penalised. Walk `page` or set `date_from` to cover more.
- Market-ban decisions (市场禁入决定) are against individuals and are not in this pack.
- The publisher's server sometimes answers slowly or not at all from some networks; a timeout or non-JSON answer is reported as `upstream_down`, never as an empty result.
- Text is the Commission's own wording, in simplified Chinese.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"cn-csrc-actions": {
"url": "https://gateway.pipeworx.io/cn-csrc-actions/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/cn-csrc-actions/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_csrc_enforcement_search \
-H 'Content-Type: application/json' \
-d '{"query":"佳缘","date_from":"2026-09-01","limit":3}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/cn_csrc_enforcement_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-cn-csrc-actions` 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-csrc-actions/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"cn-csrc-actions": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-cn-csrc-actions"]
}
}
}
```
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 Csrc Actions 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