cn-nhsa-exposures
by pipeworx-io
README.md
# @pipeworx/cn-nhsa-exposures
Has China's National Healthcare Security Administration (国家医疗保障局) publicly named this hospital, clinic or pharmacy in a medical-insurance fund fraud case: what it did and how it was handled (contract terminated, funds recovered)? Rows are the Administration's published exposure bulletins (曝光台) and typical-case releases, newest first. Firms and institutions 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_nhsa_exposures_search(query?, skip?, limit?)` -- one call reads the Administration's release list (about 35 releases, 2019 onward), then up to `limit` (1-3) releases starting at `skip` newest-first. Each institution case gives the case title, the institution, a summary of the conduct and the handling the Administration states, and the link to the official release. `query` is Chinese text matched only within the releases read (the publisher offers no keyword search); `skip` moves back in time. Also returns `searched` (releases in the list, how many were read, the dates covered, how many were not read), `individual_cases_omitted`, `unclassified_cases_omitted`, `person_sentences_omitted`, `unread_notices` and `data_as_of`.
- `cn_nhsa_exposures_get(notice_url, query?)` -- reads one release in full (institution cases only), from a `notice_url` returned by the search.
## Auth
Keyless.
## Data sources
- National Healthcare Security Administration (国家医疗保障局), exposure bulletins and typical cases on medical-insurance fund fraud (曝光台、典型案例). Read from the publisher on each call; nothing is stored.
## Individuals are not returned
Most published cases concern insured people, doctors or staff. A case about a natural person is left out and counted (`individual_cases_omitted`). A case that cannot be classified is left out and counted (`unclassified_cases_omitted`). In an institution case, sentences about people (court sentences, named staff) are dropped and counted (`person_sentences_omitted`). Every response carries a `note` saying so; the tests prove that a person's name and sentence never appear in a response.
## Behaviour worth knowing
- The cases are a selection the Administration chose to publish, not a register of every penalty. No match is never evidence that an institution was not penalised.
- The newest releases (2025 onward) mostly concern individuals or pharmacies by batch; the older bulletins hold most hospital cases, so use `skip`.
- A release 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.
- Text is the Administration's own wording, in simplified Chinese. Court details are left out.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"cn-nhsa-exposures": {
"url": "https://gateway.pipeworx.io/cn-nhsa-exposures/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/cn-nhsa-exposures/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_nhsa_exposures_search \
-H 'Content-Type: application/json' \
-d '{"skip":17,"limit":1}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/cn_nhsa_exposures_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-cn-nhsa-exposures` 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-nhsa-exposures/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"cn-nhsa-exposures": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-cn-nhsa-exposures"]
}
}
}
```
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 Nhsa Exposures 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