@pipeworx/jp-recalls
by pipeworx-io
README.md
# @pipeworx/jp-recalls
Japan's consumer product recall notices (リコール情報): recalls, refunds, repairs and replacements of food, appliances, household goods, clothing, vehicles and other consumer products, as published by the Consumer Affairs Agency (消費者庁).
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
- `jp_recalls_search(query?, category?, date_from?, date_to?, limit?, page?)` -- search the recall list by Japanese keyword (full-width and half-width are normalised), optionally within one category. Returns id, title, company, product, remedy type, category, posting date and action start date, plus `data_as_of`, the list searched and the total the publisher reports. With no keyword and no category it returns the newly registered list. One page per call; date filters apply to the fetched page and the response says how many rows they hid.
- `jp_recall_get(id)` -- one notice in full: product, company, remedy, reason and hazard, affected models/lots/quantity as stated, action start date, the referring ministry and the link to the official notice. Unknown id returns `found:false`.
## Auth
Keyless.
## Data sources
- Consumer Affairs Agency (消費者庁), Japan: recall information site, which brings together recall notices filed by the ministries responsible for each product area.
Read live per request; nothing is stored. The text of each notice is Japanese.
Traps worth knowing:
- The publisher's search is a plain form post, and an empty keyword with no category is refused by the publisher, so the pack switches to the newly registered list in that case.
- The publisher caps the keyword at 30 characters and does not match half-width katakana; the pack normalises first.
- Company contact details on a notice are deliberately not returned. The notice link has them.
- Recall notices are issued by many ministries (METI for electrical goods, MHLW for food, MLIT for vehicles); this site lists them together, so vehicle recalls here are the consumer-facing summary, not the full transport ministry register.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"jp-recalls": {
"url": "https://gateway.pipeworx.io/jp-recalls/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/jp-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/jp_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/jp_recalls_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-jp-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/jp-recalls/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"jp-recalls": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-jp-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 Jp 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