Skip to main content
Glama
sg-hsa-recalls

sg-hsa-recalls

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

Singapore Health Sciences Authority product recalls and safety alerts for health products supplied in Singapore: medicines (therapeutic products), medical devices, health supplements, cosmetics, traditional and Chinese proprietary medicines. About 430 notices from 2007 onwards.

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.

## Tools

- `sg_hsa_recalls_search(query?, kind?, product_type?, year?, limit?)` -- searches the Authority's announcements, keeping only the Product Recalls and Safety Alerts categories, newest first. Each hit: id, date, kind (recall or safety alert), title, product type, a short description (product, registration number, batch, reason) and the link. The list does not carry the company. `searched` states how many announcements were read and how many were left out as other categories.
- `sg_hsa_recall_get(id)` -- one notice by id (such as `recall-of-meravo-film-coated-tablet-100mg`): date of recall, product, active ingredient, product category, registration number, batch, class and level of recall, the local company that supplies the product, the description of the issue and the recall instructions. An unknown id is `found:false`.

Every response carries `source` and `data_as_of`.

## Auth

Keyless.

## Data sources

- Health Sciences Authority (Singapore), announcements: product recalls and safety alerts. Read live per call, nothing stored.

Registered-product data for Singapore is in `hsa-singapore`; this pack is the recall and alert notices.

Privacy: companies and products only. Press releases and enforcement news are excluded, so no individuals appear; phone-number-shaped and e-mail-shaped text is removed.

Traps worth knowing: the search reads the Authority's announcements page in one request (it is a large page); a page that carries no announcement index is an error, never no match; zero matches means no match in the published list, not that a product is safe; a safety alert may have no recall details table.

## Quick Start

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

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

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/sg-hsa-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_hsa_recalls_search \
  -H 'Content-Type: application/json' \
  -d '{"query":"tablet","year":2026}'
```

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

## Run it from npm

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

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