kr-recalls
by pipeworx-io
README.md
# @pipeworx/kr-recalls
South Korea's domestic product recall notices (국내리콜): voluntary and ordered recalls of consumer products, children's products, batteries and electrical goods, as published by the Korea Agency for Technology and Standards (KATS) Product Safety Information Center.
Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2018+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
## Tools
- `kr_recalls_search(query?, search_in?, date_from?, date_to?, limit?, page?)` -- search the recall list by Korean keyword across everything or one field (`model`, `product`, `company`, `barcode`, `certification_no`), or by a closed publication date range. Newest first, ten rows per page. Returns id, product, model or name, company, recall type, barcode and publication date, plus `data_as_of`, the list searched and the page count. Zero matches say which list was searched.
- `kr_recall_get(id)` -- one notice: recall type, product category, model, brand, origin, recalling company, certification number, and the defect, hazard and consumer action as stated. Unknown id returns `found:false`.
## Auth
Keyless.
## Data sources
- Korea Agency for Technology and Standards (KATS), Product Safety Information Center: domestic recall notices.
Read live per request; nothing is stored. Text is Korean.
Traps worth knowing:
- The publisher matches Korean text only and ignores spaces; the pack removes spaces and the characters the publisher refuses, and reports the keyword it actually used in `query_used`.
- A date range cannot be combined with a keyword upstream; when both are given the keyword filters the fetched page only.
- The notice page has no publication date; the list row does.
- The representative's name is not returned, and phone numbers inside notice text are replaced.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"kr-recalls": {
"url": "https://gateway.pipeworx.io/kr-recalls/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/kr-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 2018+ 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/kr_recalls_search \
-H 'Content-Type: application/json' \
-d '{"query":"보조배터리","limit":5}'
```
No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/kr_recalls_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-kr-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/kr-recalls/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"kr-recalls": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-kr-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 Kr 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
ResponsivenessNo recent community issues