Skip to content

Restaurant Health Inspection Scores MCP server

io.github.theluckystrike/restaurant-health-inspection-scores-mcptheluckystrikestreamable-httpv1.0.0Scanned

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

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Restaurant Health Inspection Scores MCP server can do

The Restaurant Health Inspection Scores MCP server is published by the GitHub account theluckystrike. It has 4 tools. It can create or change data (3 tools: restaurant_inspection_history, restaurant_inspection_failures and restaurant_inspection_cities), but cannot delete data. 1 tool only reads.

4 tools bring in text other people can write (restaurant_inspection_search, restaurant_inspection_history, restaurant_inspection_failures and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • restaurant_inspection_citiesThe 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 pub…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Covered cities
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • restaurant_inspection_failuresRecent 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 …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Recent failed inspections
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • restaurant_inspection_historyInspection 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…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Restaurant inspection history
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including restaurant_inspection_history (write), restaurant_inspection_failures (write), restaurant_inspection_cities (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http restaurant-health-inspection-scores https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp
claude mcp add --transport http restaurant-health-inspection-scores https://restaurant-health-inspection-scores-mcp.lipmichal.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__restaurant-health-inspection-scores__restaurant_inspection_search"
    ],
    "ask": [
      "mcp__restaurant-health-inspection-scores__restaurant_inspection_history",
      "mcp__restaurant-health-inspection-scores__restaurant_inspection_failures",
      "mcp__restaurant-health-inspection-scores__restaurant_inspection_cities"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as restaurant-health-inspection-scores. Review it before you use it.

Capability tags behind 4 rules
  • mcp__restaurant-health-inspection-scores__restaurant_inspection_search untrusted-input
  • mcp__restaurant-health-inspection-scores__restaurant_inspection_history untrusted-input
  • mcp__restaurant-health-inspection-scores__restaurant_inspection_failures untrusted-input
  • mcp__restaurant-health-inspection-scores__restaurant_inspection_cities untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/restaurant-health-inspection-scores-mcp/verify?hash=5e2bf229d4e7aa14deccc076ef28b6db9f4e28b474144a0a0c5cb17a85ae4845" | jq -e '.changed == false'

Pinned hash 5e2bf229d4e7, from Nov 17, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/restaurant-health-inspection-scores-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/restaurant-health-inspection-scores-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/restaurant-health-inspection-scores-mcp.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/restaurant-health-inspection-scores-mcp)

Source: MCP Registry · repository. Synced Nov 17, 2026, 16:18 UTC.

Restaurant Health Inspection Scores MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Restaurant Health Inspection Scores MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Restaurant Health Inspection Scores MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Restaurant Health Inspection Scores MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Restaurant Health Inspection Scores MCP server have?

4 tools: 3 write, 1 read. restaurant_inspection_history, restaurant_inspection_failures, restaurant_inspection_cities and restaurant_inspection_search.

Does the Restaurant Health Inspection Scores MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Restaurant Health Inspection Scores MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Restaurant Health Inspection Scores MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.