nz-recalls
by pipeworx-io
README.md
# @pipeworx/nz-recalls
New Zealand's government product recalls register, run by MBIE Product Safety: about 1,600 consumer product recalls (children's toys, baby products, appliances, electric and gas products, vehicles, cosmetics, tools, sports gear, building products) with the hazard, what consumers should do, the barcodes and where the product was sold.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2015+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `nz_recalls_search(query?, category?, sort?, page?)` -- searches the register, 12 recalls per page, newest first. `category` is one of airbags, appliances, baby, building, chemicals, toys, clothing, cosmetics, electric_gas, home, medical, office, sand, sports, tools, vehicles; `sort` is latest, oldest, az or za. Each hit: id, title, recall date, categories, link. `total_matching` counts the whole filtered register. Zero matches states what was searched.
- `nz_recall_get(id)` -- one recall by its id (the path slug from the search): recall date, categories, product identifiers (barcodes, SKUs, retailers and sale period), supplier company, hazard, what to do, safety-tip links. An unknown id is `found:false`.
Every response carries `source` and `data_as_of` (the newest recall date in the page).
## Auth
Keyless.
## Data sources
- MBIE Product Safety (New Zealand), consumer product recalls register. Read live per call, nothing stored.
Covers consumer products recalled in New Zealand, including vehicle and airbag recalls listed by the register. Food recalls are a different list (MPI) and medicines are issued by Medsafe.
Privacy: supplier and retailer company names are returned; phone numbers and e-mail addresses are removed from every text field.
Traps worth knowing: the keyword is the register's own text search, so it matches words in the notice body as well as the title; a zero-match search means no entry in this register, not that a product is safe; some recalls list dozens of retailers inside `product_identifiers`.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"nz-recalls": {
"url": "https://gateway.pipeworx.io/nz-recalls/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/nz-recalls/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 2015+ 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/nz_recalls_search \
-H 'Content-Type: application/json' \
-d '{"query":"lamp","category":"toys"}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/nz_recalls_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-nz-recalls` 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/nz-recalls/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"nz-recalls": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-nz-recalls"]
}
}
}
```
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 Nz Recalls 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
ResponsivenessOutdated data