hk-food-alerts
by pipeworx-io
README.md
# @pipeworx/hk-food-alerts
Hong Kong's Centre for Food Safety food alerts and allergy alerts: products the Centre tells the public not to consume (Listeria, Salmonella, veterinary drug residues, aflatoxins, heavy metals, undeclared allergens, labelling breaches), 2006 onwards, with the importer, the test result against the legal limit, the action taken and the advice to the trade and to consumers.
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_food_alerts_search(query?, alert_type?, year?, date_from?, date_to?, limit?)` -- searches the alert list, newest first. One calendar year is read per list page: by default the current list, with `year` an earlier one, or a `date_from` / `date_to` window of up to three years. `alert_type` is food, allergy or all (types are recorded from 2021). The keyword matches alert titles. Each hit: id, date, type, title, link. Zero matches states which years were read.
- `hk_food_alert_get(id)` -- one alert by its id (such as `2026_636`): issue date, food product, importer, place of origin, product description, reason, action taken, advice to trade and consumers, related links. An unknown id is `found:false`.
Every response carries `source` and `data_as_of` (the newest alert date scanned).
## Auth
Keyless.
## Data sources
- Centre for Food Safety, Food and Environmental Hygiene Department (Hong Kong), food alerts and allergy alerts. Read live per call, nothing stored.
Covers food products in Hong Kong. Consumer goods safety notices are issued by the Customs and Excise Department and are not covered here.
Privacy: importer company names are returned; phone numbers and e-mail addresses are removed from every text field.
Traps worth knowing: a search reads only the years it reports in `searched.years_read`; a zero-match search means no alert in those years, not that a food is safe; product names and brands are often "(Not available in English)".
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"hk-food-alerts": {
"url": "https://gateway.pipeworx.io/hk-food-alerts/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/hk-food-alerts/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_food_alerts_search \
-H 'Content-Type: application/json' \
-d '{"query":"cheese","year":2026}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/hk_food_alerts_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-hk-food-alerts` 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-food-alerts/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"hk-food-alerts": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-hk-food-alerts"]
}
}
}
```
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 Food Alerts 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