hk-afrc-discipline
by pipeworx-io
README.md
# @pipeworx/hk-afrc-discipline
Hong Kong Accounting and Financial Reporting Council (AFRC) disciplinary cases against audit and accounting firms: the misconduct found, the sanctions (public reprimand, practice limitation, pecuniary penalty, directions) and the statement of disciplinary action, from 2023.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2007+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `hk_afrc_cases_search(query?, year?, limit?)` -- searches the cases, newest first. The keyword matches the firm name and the misconduct text. Each hit: case id, date, firms, a one-line misconduct summary, penalties in HK$, links to the press release and the statement. `individuals_dropped` and `cases_without_a_firm` count what was not returned.
- `hk_afrc_case_get(id)` -- one case by its id (such as `2026-04-23-pricewaterhousecoopers`): firm names, full misconduct findings, the sanctions on the firm, penalties and links. An unknown id is `found:false`.
Every response carries `source` and `data_as_of` (the newest case date).
## Auth
Keyless.
## Data sources
- Accounting and Financial Reporting Council (Hong Kong), disciplinary cases. Read live per call, nothing stored.
Privacy: firms only. AFRC cases name the firm and the individual CPAs together, and some cases are against individuals alone. Individual regulatees are dropped and counted, cases with no firm are skipped and counted, sanction lines about an individual are withheld (`sanction_lines_withheld`), and an individual's name found in the misconduct or sanction text is replaced with `[individual]`. A regulatee counts as a firm only when its name carries a practice marker (Limited, CPA, &, Co., a network name); anything else is treated as a person.
Traps worth knowing: a zero-match search means no match among the firm cases listed, not that a firm has a clean record; two cases on one day for the same firm get a numeric suffix on the id.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"hk-afrc-discipline": {
"url": "https://gateway.pipeworx.io/hk-afrc-discipline/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/hk-afrc-discipline/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 2007+ 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/hk_afrc_cases_search \
-H 'Content-Type: application/json' \
-d '{"query":"PricewaterhouseCoopers"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/hk_afrc_cases_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-hk-afrc-discipline` 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/hk-afrc-discipline/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"hk-afrc-discipline": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-hk-afrc-discipline"]
}
}
}
```
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 Hk Afrc Discipline 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