cn-nfra-penalties
by pipeworx-io
README.md
# @pipeworx/cn-nfra-penalties
Which banks, insurers and other financial firms has China's financial regulator (国家金融监督管理总局, the National Financial Regulatory Administration, formerly the CBIRC) fined, for what conduct, and how much? Rows are its published administrative penalty disclosures (行政处罚信息公开), from the head office, the provincial bureaus and the sub-bureaus. 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_nfra_penalties_search(query?, date_from?, date_to?, level?, page?, limit?)` -- lists disclosure batches newest first: batch id, title, issuing bureau, publication date and the link to the official notice. `level` is `head_office` (default), `provincial_bureau` or `sub_bureau`. One request reads one page of 20 batches. The publisher offers no keyword or date search: `query` (Chinese, e.g. a bureau name) is matched against the batch titles on the page read, `date_from`/`date_to` trim the page, `page` moves through the list. Also returns `searched` (page, page count, dates covered) and `data_as_of`.
- `cn_nfra_penalty_get(id, firm?)` -- one batch (id from the search; two requests are never needed, one is). For each firm: the conduct as the regulator states it, the penalty as stated in the original Chinese, `penalty_amount_cny` when exactly one fine amount is stated for that firm, the deciding authority and the link to the official notice. `firm` keeps rows whose firm name contains that Chinese text. An unknown id is `found:false`; a batch that is not a penalty table (a narrative summary, a notice-delivery announcement) is `found:true` with `empty_reason:"unread"` and the link, never an empty list.
## Auth
Keyless.
## Data sources
- National Financial Regulatory Administration (国家金融监督管理总局), administrative penalty information disclosure (行政处罚信息公开). Read from the publisher on each call; nothing is stored.
## Individuals are not returned
The regulator fines a bank and its managers in the same row. This pack returns firms and organisations only:
- A row whose party is a natural person is dropped (counted in `individuals_omitted`).
- In a row naming a firm and its responsible people, only the penalty clauses addressed to the firm are returned; the people's names, roles and clauses are dropped (clauses counted in `people_clauses_omitted`). A person's name that appears in the conduct text is removed.
- A party or clause the pack cannot classify is left out and counted in `skipped_possible_individuals`. A clause with no named subject beside people is not attributed to the firm.
- No ID numbers, addresses or contact details are read or returned.
Every response carries a `note` saying so; the tests assert that fixture individuals never appear anywhere in a response, free text included.
## Behaviour worth knowing
- A search covers one page. No match means no match on that page (`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. Find a firm by opening batches with `cn_nfra_penalty_get` and `firm`.
- The data is Chinese-language. An English query matches nothing; the response says so.
- Two layouts are read: the multi-row batch table, and the older single-case notice. Decisions before 2023 (the predecessor regulators) and narrative summaries are reported as unread.
- Provincial and sub-bureau batches name branches ("该支行") as the penalised party; the firm name is returned as the publisher states it, the branch included.
- `penalty_amount_cny` is only the fine; confiscation and warnings stay in the stated `penalty` text. When a firm row states several fines (head office and branches), the amount is null and the text carries them.
- The publisher's server can be slow from some networks; one bounded retry covers network and edge failures, anything else is `upstream_down`, never an empty result.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"cn-nfra-penalties": {
"url": "https://gateway.pipeworx.io/cn-nfra-penalties/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/cn-nfra-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_nfra_penalties_search \
-H 'Content-Type: application/json' \
-d '{"level":"head_office","limit":3}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/cn_nfra_penalties_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-cn-nfra-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-nfra-penalties/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"cn-nfra-penalties": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-cn-nfra-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 Nfra 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