Skip to main content
Glama
sg-product-recalls

sg-product-recalls

by pipeworx-io
README.md
# @pipeworx/sg-product-recalls

Singapore's Consumer Product Safety Office safety alerts and product recalls for consumer goods sold in Singapore: children's toys and apparel, furniture, electrical products, power banks, recreational products and others. For each notice: the date, whether it is a recall or a safety alert, the category, the title, the company and product where the title names them, the hazard where the title states it, and the link to the notice.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2016+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

**List only.** The Office publishes each notice as a PDF. This pack reads the dated list, not the notice text, and every response says so (`notice_text_read: false`). Open `notice_url` for the hazard details and the remedy.

## Tools

- `sg_product_recalls_search(query?, category?, kind?, date_from?, date_to?, limit?)` -- searches the lists, newest first. `category` is one of children-apparel, children-toys, electrical, furniture, power-banks, recreational-products, others, or all (the default, which reads every category list). `kind` is recall, alert or all. The keyword matches the title and company. Zero matches names the lists read; a list that cannot be read is reported under `partial`, never as no match.

Every response carries `source`, `data_as_of` (the newest notice date scanned) and `individuals_dropped`.

## Auth

Keyless.

## Data sources

- Consumer Product Safety Office (Singapore), safety alerts and recalls lists. Read live per call, nothing stored.

Covers consumer goods. Food recalls are in `sg-food-recalls`; health-product recalls are in `sg-hsa-recalls`.

Privacy: firms and products only. The lists carry no individuals; phone-number-shaped and e-mail-shaped text is removed from every title.

Traps worth knowing: company and product come from the title and are null when the title does not name a company first; a search reads the lists as published, so an old notice the Office has removed is absent; zero matches means no match in the lists read, not that a product is safe.

## Quick Start

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

```json
{
  "mcpServers": {
    "sg-product-recalls": {
      "url": "https://gateway.pipeworx.io/sg-product-recalls/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/sg-product-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 2016+ 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/sg_product_recalls_search \
  -H 'Content-Type: application/json' \
  -d '{"query":"IKEA","category":"furniture"}'
```

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

## Run it from npm

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

```json
{
  "mcpServers": {
    "sg-product-recalls": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-sg-product-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 Sg Product 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