# Restaurant Health Inspection Scores MCP (remote · restaurant-health-inspection-scores-mcp.lipmichal.workers.dev)

Restaurant health inspection grades, scores, violations, closures: NYC, Chicago, Austin, Boston.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `restaurant-health-inspection-scores-mcp.lipmichal.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-restaurant-health-inspection-scores-mcp/restaurant-health-inspection-scores-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-restaurant-health-inspection-scores-mcp/restaurant-health-inspection-scores-mcp)

## Channel facts

- Endpoint: `https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/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 405, 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 855 tokens (~213/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Inspection Scores MCP server?

Restaurant Health Inspection Scores MCP is a hosted endpoint at https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/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 theluckystrike-restaurant-health-inspection-scor 'https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-restaurant-health-inspection-scor": {
      "url": "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-restaurant-health-inspection-scor": {
      "type": "http",
      "url": "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-restaurant-health-inspection-scor]
url = "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-restaurant-health-inspection-scor": {
      "type": "remote",
      "url": "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-restaurant-health-inspection-scor --url 'https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-restaurant-health-inspection-scor:
    url: "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-restaurant-health-inspection-scor": {
      "Transport": "http",
      "Url": "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-restaurant-health-inspection-scor -t streamable-http -u 'https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-restaurant-health-inspection-scor": {
      "type": "http",
      "url": "https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/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-21 (score 67, +1)

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

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

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

### 2026-11-18 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 65)

First indexed and scored.

## MCP tools (4)

### `restaurant_inspection_search` (~224 tokens)

Restaurant health inspection lookup

Find restaurants and other food establishments by name and return each one's latest health inspection: in New York City the posted letter grade (A, B, C or pending) and the score in points, in Chicago Pass, Pass w/ Conditions or Fail, in Austin the score out of 100, in Boston the pass/fail result and open violations. Without a city or ZIP it searches all four cities. Returns the id for restaurant_inspection_history.

Input parameters:

- `address` (string): Street words to narrow a chain, e.g. "Houston" or "350 5th Ave".
- `city` (string): New York City (or Manhattan, Brooklyn, Queens, Bronx, Staten Island), Chicago, Austin or Boston (or a Boston neighborhood).
- `limit` (integer): How many establishments to return. Default 10.
- `name` (string, required): Restaurant name or part of it, e.g. "Katz's Delicatessen" or "Au Cheval".
- `zip` (string|number): 5-digit ZIP code in a covered city.

### `restaurant_inspection_history` (~243 tokens)

Restaurant inspection history and violations

Inspection record of one establishment by city and id (from restaurant_inspection_search), or by city and name: the latest inspection with every violation cited (NYC critical flags, Chicago inspector comments, Boston violation level * to *** and whether it was corrected), the current NYC letter grade, past inspections with scores or results, and how many inspections in the last 3 years failed or ended in a closure. Austin publishes scores only.

Input parameters:

- `address` (string): Street words to pick one location of a chain when searching by name.
- `city` (string): New York City (or Manhattan, Brooklyn, Queens, Bronx, Staten Island), Chicago, Austin or Boston (or a Boston neighborhood).
- `id` (string|number): Establishment id from restaurant_inspection_search: NYC CAMIS, Chicago license number, Austin facility id or Boston license number.
- `inspections` (integer): How many past inspections to return. Default 8.
- `name` (string): Name, used when no id is given; the best match is used and other matches are listed.
- `zip` (string|number): 5-digit ZIP code in a covered city.

### `restaurant_inspection_failures` (~170 tokens)

Recent failed restaurant inspections and closures

Recent failed health inspections in a city, NYC borough or ZIP code over the last N days up to the newest published inspection: New York City Health Department closures and scores of 28 points or more (C range), Chicago inspections with the result Fail, Austin scores under 70, Boston failed inspections and closures. Newest first, with each establishment's id.

Input parameters:

- `city` (string): New York City (or Manhattan, Brooklyn, Queens, Bronx, Staten Island), Chicago, Austin or Boston (or a Boston neighborhood).
- `days` (integer): Window in days, ending at the newest published inspection. Default 30.
- `limit` (integer): How many to list. Default 15.
- `zip` (string|number): 5-digit ZIP code in a covered city.

### `restaurant_inspection_cities` (~57 tokens)

Covered cities and grading scales

The cities this server covers (New York City, Chicago, Austin, Boston), how each health department scores or grades an inspection, what detail its open data has, and the newest published inspection date in each dataset (read live).

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65

## Common questions

### What is the Restaurant Health Inspection Scores MCP server?

Restaurant Health Inspection Scores MCP is listed in the public MCP registry as io.github.theluckystrike/restaurant-health-inspection-score…. Restaurant health inspection grades, scores, violations, closures: NYC, Chicago, Austin, Boston. This page covers its hosted endpoint (https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp).

### Is the Restaurant Health Inspection Scores MCP server safe to use?

Restaurant Health Inspection Scores MCP scores 67 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 Inspection Scores MCP server expose?

Restaurant Health Inspection Scores MCP exposes 4 tools: restaurant_inspection_search, restaurant_inspection_history, restaurant_inspection_failures, restaurant_inspection_cities. Their descriptions and schemas cost roughly 694 tokens of context every time the server is loaded.

### Does the Restaurant Health Inspection Scores MCP server require authentication?

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

### Is the Restaurant Health Inspection Scores MCP server still maintained?

Restaurant Health Inspection Scores MCP 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 Inspection Scores MCP server?

VerifyMCP ran 12 checks on Restaurant Health Inspection Scores MCP, 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 Inspection Scores MCP: 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://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/restaurant-health-inspection-scores-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-restaurant-health-inspection-scores-mcp/restaurant-health-inspection-scores-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-restaurant-health-inspection-scores-mcp/restaurant-health-inspection-scores-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-restaurant-health-inspection-scores-mcp/restaurant-health-inspection-scores-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-restaurant-health-inspection-scores-mcp/restaurant-health-inspection-scores-mcp
