mcpField
U
Uk Food Hygiene

Uk Food Hygiene

Remote
pipeworx.ioHealth0Updated 5w ago

About Uk Food Hygiene

Uk Food Hygiene is an MCP service for clients and agents looking up hygiene ratings for UK food businesses, using data from the Food Standards Agency FHRS. It supports searches by name, address, or location and provides full inspection records for individual establishments.

Key features

  1. 01Search by name, address, or location
  2. 02Filter by business type and minimum rating
  3. 03View ratings and inspection dates
  4. 04Retrieve full records and sub-scores

Use cases

  1. 01Compare ratings of nearby restaurants
  2. 02Check ratings for takeaways or pubs
  3. 03Review an establishment’s inspection details

MCP support

It exposes Food Standards Agency FHRS search and detail tools to MCP clients. It can connect through the Pipeworx gateway or run as a local stdio MCP server.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/uk-food-hygiene/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-uk-food-hygiene

UK Food Hygiene MCP — Food Standards Agency food hygiene ratings (FHRS)

Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.

Tools

ToolDescription
uk_food_hygiene_searchSearch UK restaurant food hygiene ratings from the Food Standards Agency FHRS — answers "is this restaurant clean", "is this takeaway safe to eat at", "food hygiene rating of X". Search by business name and/or address (a town, street, or postcode works), or by latitude/longitude + radius_miles for hygiene ratings near a point. Filter by business_type (restaurant, takeaway, pub, hotel, supermarket, mobile caterer...) and min_rating (1-5). Returns rating (0-5 in England/Wales/NI; Scotland uses "Pass"/"Improvement Required" under FHIS), inspection date, address, and inspection sub-scores. Example: uk_food_hygiene_search({ name: "Nandos", address: "Leeds" })
uk_food_hygiene_detailsGet the full Food Standards Agency FHRS inspection record for one UK establishment by its FHRSID (from uk_food_hygiene_search) — rating, inspection date, sub-scores for hygiene / structural compliance / confidence in management (0 = best, higher = worse), full address, local authority contact, and geocode. Use to check how clean or safe a specific UK restaurant, takeaway, cafe, or pub is. Example: uk_food_hygiene_details({ fhrsid: 537122 })

Quick Start

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

{
  "mcpServers": {
    "uk-food-hygiene": {
      "url": "https://gateway.pipeworx.io/uk-food-hygiene/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/uk-food-hygiene/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 1684+ 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

curl -X POST https://gateway.pipeworx.io/v1/tools/uk_food_hygiene_search \
  -H 'Content-Type: application/json' \
  -d '{"name":"Nandos","address":"Leeds"}'

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

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "uk-food-hygiene": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-uk-food-hygiene"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-uk-food-hygiene

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 Uk Food Hygiene data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.