# Restaurant Health Inspections (remote · food.ian.sh)

Restaurant health inspection grades and violations for 20 US, UK, Canadian and French locations.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `food.ian.sh`: 68/100 (this document), [markdown](https://verifymcp.io/servers/iangcarroll-restaurant-health/food.md), [page](https://verifymcp.io/servers/iangcarroll-restaurant-health/food)

## Channel facts

- Endpoint: `https://food.ian.sh/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1160 tokens (~386/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Restaurant Health Inspections MCP server?

Restaurant Health Inspections is a hosted endpoint at https://food.ian.sh/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http iangcarroll-restaurant-health 'https://food.ian.sh/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "iangcarroll-restaurant-health": {
      "url": "https://food.ian.sh/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "iangcarroll-restaurant-health": {
      "type": "http",
      "url": "https://food.ian.sh/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.iangcarroll-restaurant-health]
url = "https://food.ian.sh/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "iangcarroll-restaurant-health": {
      "type": "remote",
      "url": "https://food.ian.sh/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add iangcarroll-restaurant-health --url 'https://food.ian.sh/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  iangcarroll-restaurant-health:
    url: "https://food.ian.sh/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "iangcarroll-restaurant-health": {
      "Transport": "http",
      "Url": "https://food.ian.sh/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add iangcarroll-restaurant-health -t streamable-http -u 'https://food.ian.sh/mcp'
```

### Other

```json
{
  "mcpServers": {
    "iangcarroll-restaurant-health": {
      "type": "http",
      "url": "https://food.ian.sh/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-10 (score 63)

First indexed and scored.

## MCP tools (3)

### `search_restaurants` (~444 tokens)

Search restaurants

Find restaurants by name and get their current health grade / rating. Returns matching establishments with an `id` to pass to get_inspection_history.

Input parameters:

- `address` (string): Optional words that must appear in the street address (e.g. "broadway").
- `city` (string, required): "nyc" (New York City, New York, US), "sf" (San Francisco, California, US), "la" (Los Angeles County, California, US), "las_vegas" (Las Vegas, Clark County, Nevada, US), "chicago" (Chicago, Illinois,…
- `limit` (integer): Max results (default 10, max 50).
- `name` (string, required): Restaurant name or part of it, as a phrase. Case, spaces and punctuation are ignored, so "in n out" matches "IN-N-OUT BURGER" and "katzs" matches "KATZ'S".
- `zip_code` (string): Optional ZIP/postal code filter (ignored for: sf, sacramento).

### `get_inspection_history` (~558 tokens)

Inspection history

Get the inspection history (dates, scores/grades/results, and violations where published) for one restaurant.

Input parameters:

- `city` (string, required): "nyc" (New York City, New York, US), "sf" (San Francisco, California, US), "la" (Los Angeles County, California, US), "las_vegas" (Las Vegas, Clark County, Nevada, US), "chicago" (Chicago, Illinois,…
- `max_inspections` (integer): Max inspections to return, newest first (default 10).
- `restaurant_id` (string, required): The `id` from search_restaurants (nyc: NYC CAMIS number; sf: SF permit number; la: LA record id like PR0012345; las_vegas: Southern Nevada permit number; chicago: Chicago license number; boston: Bost…

### `rating_systems` (~31 tokens)

Rating systems

List the supported cities and explain how each one's health grades, scores or results work (they differ a lot).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/iangcarroll-restaurant-health/food#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 66
- 2026-11-16: 66
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 64
- 2026-11-11: 64
- 2026-11-10: 63

## Common questions

### What is the Restaurant Health Inspections MCP server?

Restaurant Health Inspections is an MCP server listed in the public MCP registry as io.github.iangcarroll/restaurant-health. Restaurant health inspection grades and violations for 20 US, UK, Canadian and French locations. This page covers its hosted endpoint (https://food.ian.sh/mcp).

### Is the Restaurant Health Inspections MCP server safe to use?

Restaurant Health Inspections scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Restaurant Health Inspections MCP server expose?

Restaurant Health Inspections exposes 3 tools: search_restaurants, get_inspection_history, rating_systems. Their descriptions and schemas cost roughly 1,033 tokens of context every time the server is loaded.

### Does the Restaurant Health Inspections MCP server require authentication?

No. We connected to Restaurant Health Inspections without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Restaurant Health Inspections MCP server still maintained?

Restaurant Health Inspections is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Restaurant Health Inspections MCP server?

VerifyMCP ran 12 checks on Restaurant Health Inspections, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Restaurant Health Inspections: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://food.ian.sh/mcp
- Repository: https://github.com/iangcarroll/food
- Website: https://food.ian.sh/
- Changelog RSS feed: https://verifymcp.io/servers/iangcarroll-restaurant-health/food.xml
- Changelog JSON feed: https://verifymcp.io/servers/iangcarroll-restaurant-health/food/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/iangcarroll-restaurant-health/food.json
- HTML version of this page: https://verifymcp.io/servers/iangcarroll-restaurant-health/food
