Skip to content
Back to search

mcp-uk-food-alerts

uk-food-alerts -- the Food Standards Agency's food alerts for England, Wales and Northern Ireland: product recalls and withdrawals (PRIN, Product Recall Information Notices), allergy alerts (AA) and food alerts for action (FAFA).

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-food-alerts/badge.svg)](/listings/pipeworx-io--mcp-uk-food-alerts)

HTML

<a href="/listings/pipeworx-io--mcp-uk-food-alerts"><img src="/api/listings/pipeworx-io--mcp-uk-food-alerts/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-food-alerts": {
      "url": "https://gateway.pipeworx.io/uk-food-alerts/mcp"
    }
  }
}

What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/uk-food-alerts/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 · 129 lines
  1. # @pipeworx/uk-food-alerts
  2. The UK Food Standards Agency's food alerts for England, Wales and Northern Ireland: product recalls and withdrawals, allergy alerts and food alerts for action, with the business, the products and batches affected, the action taken and the advice to consumers.
  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_food_alerts_search(query?, type?, date_from?, limit?)` — searches the alerts, newest first. `type` is `all`, `recall` (product recall information notices), `allergy` (allergy alerts) or `action` (food alerts for action). Each hit: alert number, type, title, the business, issue date, the products named, the allergens and the notice link. The service gives no total, so `returned` is capped by `limit`; narrow with `date_from`. Zero matches states what was searched.
  6. - `uk_food_alert_get(alert_number)` — one alert (such as `FSA-AA-53-2026`, or an updated notice such as `FSA-PRIN-47-2026-update-1`): description, risk statement, every product with pack size, batch codes and use-by or best-before wording, the action taken, the consumer advice, other businesses involved and attachment links. An unknown number is `found:false`.
  7. ## Auth
  8. Keyless.
  9. ## Data sources
  10. - Food Standards Agency (UK), food alerts open data (Open Government Licence v3): read live per call, nothing stored. Scotland's alerts are issued by Food Standards Scotland and are not in this list. The FSA hygiene ratings are a different dataset (`uk-food-hygiene`).
  11. Traps worth knowing: the service has no upper date bound, so only `date_from` is offered; a record's `type` is a list of strings in the search answer and a list of objects in the single-record answer (both are read); updated notices carry an `-update-N` suffix in their number.
  12. ## Quick Start
  13. Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
  14. ```json
  15. {
  16. "mcpServers": {
  17. "uk-food-alerts": {
  18. "url": "https://gateway.pipeworx.io/uk-food-alerts/mcp"
  19. }
  20. }
  21. }
  22. ```
  23. ### What this endpoint actually serves
  24. `tools/list` at `https://gateway.pipeworx.io/uk-food-alerts/mcp` returns the tools in the table
  25. above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
  26. `discover_tools`, `search_within`, `remember`/`recall` and the rest of the
  27. gateway-wide set. So the tool count you see is larger than this table: a
  28. single-pack endpoint currently lists roughly 30 shared tools alongside the
  29. pack's own. The connection's `initialize` response states its exact scope, and
  30. is the authoritative answer for a given day.
  31. This is deliberate, not multiplexing by accident. The meta-tools are what let a
  32. scoped connection answer a question this pack does not cover — via
  33. `ask_pipeworx`, which routes across the whole catalog — without you adding a
  34. second MCP server. There is currently no way to mount a pack endpoint without
  35. them; if the extra schemas cost you more context than the routing is worth,
  36. connect to the full gateway once rather than to several pack endpoints.
  37. Or connect to the full Pipeworx gateway to get every pack's tools listed
  38. directly, instead of just this one's:
  39. ```json
  40. {
  41. "mcpServers": {
  42. "pipeworx": {
  43. "url": "https://gateway.pipeworx.io/mcp"
  44. }
  45. }
  46. }
  47. ```
  48. Both URLs reach the same gateway and the same 2024+ data sources. The
  49. only difference is which pack's tools are listed **directly**; `ask_pipeworx`
  50. reaches all of them from either one.
  51. ## No MCP client? Call it over HTTP
  52. ```bash
  53. curl -X POST https://gateway.pipeworx.io/v1/tools/uk_food_alerts_search \
  54. -H 'Content-Type: application/json' \
  55. -d '{"query":"salmonella","type":"recall","date_from":"2026-01-01","limit":3}'
  56. ```
  57. No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/uk_food_alerts_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
  58. ## Run it from npm
  59. `@pipeworx/mcp-uk-food-alerts` is a local stdio bridge to the Pipeworx gateway: your MCP client
  60. starts it with `npx`, and it forwards every call to the same
  61. `https://gateway.pipeworx.io/uk-food-alerts/mcp` endpoint shown above. It needs network access;
  62. there is no offline mode.
  63. ```json
  64. {
  65. "mcpServers": {
  66. "uk-food-alerts": {
  67. "command": "npx",
  68. "args": ["-y", "@pipeworx/mcp-uk-food-alerts"]
  69. }
  70. }
  71. }
  72. ```
  73. Without a key it calls anonymously, capped at 50 calls a day. A free account
  74. raises that to 200 a day: get a key at https://pipeworx.io/signup and add
  75. `"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
  76. The key is sent as a Bearer token, the same way a hosted connection sends it,
  77. so calls are metered and billed exactly as they are there.
  78. It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
  79. also list `ask_pipeworx` and the other gateway-wide tools.
  80. Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
  81. default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
  82. your Node version's documentation.
  83. ## Using with ask_pipeworx
  84. Instead of calling tools directly, you can ask questions in plain English —
  85. this works on the pack endpoint above as well as on the full gateway:
  86. ```
  87. ask_pipeworx({ question: "your question about Uk Food Alerts data" })
  88. ```
  89. The gateway picks the right tool and fills the arguments automatically.
  90. ## More
  91. - [Docs and guides](https://pipeworx.io/docs)
  92. - [pipeworx.io](https://pipeworx.io)
  93. ## License
  94. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

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