Skip to main content
Glama
README.md
# @pipeworx/cn-pboc-penalties

Which banks, payment and clearing institutions, credit-rating agencies and other firms has the People's Bank of China (中国人民银行) fined, for what conduct, and how much? Rows are the head office's published administrative penalty disclosures (行政处罚公示), 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_pboc_penalties_search(query?, date_from?, date_to?, page?, limit?)` -- lists disclosure batches: batch id, decision-number range (银罚决字〔2026〕68-70号), publication date and the link to the official notice. One request reads one page of 20 batches. The publisher offers no keyword or date search: `query` is matched against the batch titles (decision numbers) 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_pboc_penalty_get(id, firm?)` -- one batch (one request). For each firm: decision number, the conduct as the Bank states it, the penalty as stated in the original Chinese (警告, 没收违法所得, 罚款), `penalty_amount_cny` when exactly one fine amount is stated, the deciding authority, the decision date, the publicity period and the link to the official notice. `firm` keeps rows whose firm name contains that Chinese text. An unknown id is `found:false`; a page that is not a readable penalty table is `found:true` with `empty_reason:"unread"` and the link, never an empty list.

## Auth

Keyless.

## Data sources

- People's Bank of China (中国人民银行), head office administrative penalty disclosure (行政处罚公示). Read from the publisher on each call; nothing is stored. Branch offices publish their own lists; those are not read.

## Individuals are not returned

The Bank penalises a firm and, in separate rows of the same batch, the managers and staff responsible. Those rows are published with a masked name (such as 孙某希) and the firm and department in brackets. This pack returns firms and organisations only:

- A row whose party is a natural person is dropped and counted in `individuals_omitted`; the name, the bracketed role and the individual's penalty never appear.
- A party the pack cannot classify is left out and counted in `skipped_possible_individuals`.
- A masked name that turns up in a firm row's text is removed.
- 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 (about 4 pages, 2025 to now). Batch titles are decision-number ranges, so `query` cannot find a firm; open batches with `cn_pboc_penalty_get` and its `firm` filter. No match means no match on that page (`empty_reason:"no_match_on_this_page"`, with page, page count and dates covered), never proof that a firm was not penalised.
- The data is Chinese-language; an English query matches nothing and the response says so.
- `penalty_amount_cny` is the fine only. Confiscation, warnings and criticism stay in the stated `penalty` text.
- One bounded retry covers network and edge failures; any other failure is `upstream_down`, never an empty result.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "cn-pboc-penalties": {
      "url": "https://gateway.pipeworx.io/cn-pboc-penalties/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/cn-pboc-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_pboc_penalties_search \
  -H 'Content-Type: application/json' \
  -d '{"page":1,"limit":3}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/cn_pboc_penalties_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-cn-pboc-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-pboc-penalties/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "cn-pboc-penalties": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-cn-pboc-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 Pboc 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