Skip to content
Back to search

mcp-uk-product-recalls

uk-product-recalls -- the UK Office for Product Safety and Standards' product safety alerts, product safety reports and product recalls for consumer goods, as published on the government's own site (Open Government Licence v3). Read live per call; nothing is stored.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pipeworx-io--mcp-uk-product-recalls/badge.svg)](/listings/pipeworx-io--mcp-uk-product-recalls)

HTML

<a href="/listings/pipeworx-io--mcp-uk-product-recalls"><img src="/api/listings/pipeworx-io--mcp-uk-product-recalls/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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

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

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/uk-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:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 2024+ data sources. The only difference is which pack's tools are listed **directly**; `ask_pipeworx` reaches all of them from either one.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 135 lines
  1. # @pipeworx/uk-product-recalls
  2. The UK Office for Product Safety and Standards' consumer product safety notices: product safety alerts, product safety reports and product recalls (about 3,800 notices), with the product, brand, barcodes and batch, country of origin, the hazard, the corrective action and the risk level.
  3. Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 2024+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
  4. ## Tools
  5. - `uk_product_recalls_search(query?, alert_type?, product_category?, risk_level?, date_from?, date_to?, limit?, page?)` — searches the notices, newest first. `alert_type` is `alert`, `report` or `recall`; `risk_level` is `serious`, `high`, `medium`, `low` or `not-provided`; `product_category` is one of the OPSS category slugs (toys, cosmetics, furniture, lighting-products, ...; an unknown value returns the full list). `date_from` / `date_to` filter on the notice date across the whole list. Each hit: id, type, title, category, risk level, notice date and link. `total_matching` is the count for the whole filtered list; page with `page`. Zero matches states the list, the filters and the period searched.
  6. - `uk_product_recall_get(id)` — one notice by its id (the path slug from the search): summary, product type, brand, barcodes, batch, country of origin, hazard, corrective action, PSD notification number, who notified it, measures, attachments and change history. An unknown id is `found:false`.
  7. Every response states the list searched, the period covered and `data_as_of` (the newest publication date in the page).
  8. ## Auth
  9. Keyless.
  10. ## Data sources
  11. - Office for Product Safety and Standards (UK), product safety alerts, reports and recalls, published on GOV.UK. Read live per call, nothing stored. Licence: Open Government Licence v3.0; the notices carry Crown copyright and may be reused with attribution to the Office for Product Safety and Standards.
  12. Covers consumer products in Great Britain. Food recalls are a different list (`uk-food-alerts`), and medicines and medical devices are issued by the MHRA (`mhra-alerts`).
  13. Privacy: company and brand names are returned; e-mail addresses and phone numbers in a notice's text are removed.
  14. Traps worth knowing: the notice date (`notice_date`) can differ from the publication timestamp when a notice is revised; a zero-match search means no notice in this list, not that a product is safe; a search result carries the id (a slug) rather than a numeric reference.
  15. ## Quick Start
  16. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  17. ```json
  18. {
  19. "mcpServers": {
  20. "uk-product-recalls": {
  21. "url": "https://gateway.pipeworx.io/uk-product-recalls/mcp"
  22. }
  23. }
  24. }
  25. ```
  26. ### What this endpoint actually serves
  27. `tools/list` at `https://gateway.pipeworx.io/uk-product-recalls/mcp` returns the tools in the table
  28. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  29. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  30. gateway-wide set. So the tool count you see is larger than this table: a
  31. single-pack endpoint currently lists roughly 30 shared tools alongside the
  32. pack's own. The connection's `initialize` response states its exact scope, and
  33. is the authoritative answer for a given day.
  34. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  35. scoped connection answer a question this pack does not cover — via
  36. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  37. second MCP server. There is currently no way to mount a pack endpoint without
  38. them; if the extra schemas cost you more context than the routing is worth,
  39. connect to the full gateway once rather than to several pack endpoints.
  40. Or connect to the full Pipeworx gateway to get every pack's tools listed
  41. directly, instead of just this one's:
  42. ```json
  43. {
  44. "mcpServers": {
  45. "pipeworx": {
  46. "url": "https://gateway.pipeworx.io/mcp"
  47. }
  48. }
  49. }
  50. ```
  51. Both URLs reach the same gateway and the same 2024+ data sources. The
  52. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  53. reaches all of them from either one.
  54. ## No MCP client? Call it over HTTP
  55. ```bash
  56. curl -X POST https://gateway.pipeworx.io/v1/tools/uk_product_recalls_search \
  57. -H 'Content-Type: application/json' \
  58. -d '{"query":"pushchair","alert_type":"recall","date_from":"2024-01-01","limit":3}'
  59. ```
  60. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/uk_product_recalls_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  61. ## Run it from npm
  62. `@pipeworx/mcp-uk-product-recalls` is a local stdio bridge to the Pipeworx gateway: your MCP client
  63. starts it with `npx`, and it forwards every call to the same
  64. `https://gateway.pipeworx.io/uk-product-recalls/mcp` endpoint shown above. It needs network access;
  65. there is no offline mode.
  66. ```json
  67. {
  68. "mcpServers": {
  69. "uk-product-recalls": {
  70. "command": "npx",
  71. "args": ["-y", "@pipeworx/mcp-uk-product-recalls"]
  72. }
  73. }
  74. }
  75. ```
  76. Without a key it calls anonymously, capped at 50 calls a day. A free account
  77. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  78. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  79. The key is sent as a Bearer token, the same way a hosted connection sends it,
  80. so calls are metered and billed exactly as they are there.
  81. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  82. also list `ask_pipeworx` and the other gateway-wide tools.
  83. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  84. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  85. your Node version's documentation.
  86. ## Using with ask_pipeworx
  87. Instead of calling tools directly, you can ask questions in plain English —
  88. this works on the pack endpoint above as well as on the full gateway:
  89. ```
  90. ask_pipeworx({ question: "your question about Uk Product Recalls data" })
  91. ```
  92. The gateway picks the right tool and fills the arguments automatically.
  93. ## More
  94. - [Docs and guides](https://pipeworx.io/docs)
  95. - [pipeworx.io](https://pipeworx.io)
  96. ## License
  97. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.