# `com.eatcrush/eatcrush` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/com.eatcrush/eatcrush
- JSON: https://radar.anlyon.com/api/v1/servers/com.eatcrush/eatcrush
- Version: 0.1.0 (active)
- Publisher: com.eatcrush (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-11-15T14:17:42.243Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Eatcrush
Search restaurant dishes by allergen and diet with sources and menu dates. Sydney.
```

Scanned 2026-11-15T14:18:01.194Z over streamable-http.

**4 tools: 4 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 0 | ask |
| Only reads | read | 4 | allow |

## Exfil surface

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

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | `mcp__eatcrush__get_venue` |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

No check matched anything in these tool definitions.


## Only reads (4)

Looks things up and changes nothing. Claude Code: allow.

### `compare`

- The name "compare" says "compare": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Compare one kind of dish across Sydney menus, or named venues side by side, by printed price, allergen status and distance. Examples: dish_type 'burger' with free_of ['gluten'] near 'Manly' (cheapest or nearest gluten-free burgers, with the price spread); venues ['Grill'd', 'Betty's Burgers'] with dish_type 'burger' (how many burgers each serves, how many fit, the cheapest). Prices are only what the menu prints, never estimated. Every answer links the same comparison as a table on the site (page). Menus change: tell the person to confirm with the venue.
```

### `get_venue`

- The name "get_venue" says "get": a word for reading.
- Tag private-data: The description's first sentence says "note": it reads notes.

Description, as the server wrote it:

```untrusted-server-text
Everything known about one Sydney venue: its menus and dishes with allergen status per dish, venue-wide allergen notes (dedicated fryer, shared prep), how many dishes are free of each allergen, diner ratings for coeliac and allergy friendliness, opening state, address, booking and map links, and the pages the menus were read from with dates. Use the id or slug returned by search_dishes or list_allergen_free.
```

### `list_allergen_free`

- The name "list_allergen_free" says "list": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Rank Sydney venues by how many dishes are free of one allergen (free by default, or able to be made free), optionally within a region or suburb and for one kind of dish. Examples: family 'gluten' in 'Northern Beaches'; family 'nuts' with dish_type 'dessert'; family 'dairy' in 'Inner West' with dish_type 'pasta'. Returns venues with their counts, links and the day each menu was read, plus example dishes when a dish type is given.
```

### `search_dishes`

- The name "search_dishes" says "search": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Search dishes on Sydney restaurant and cafe menus and see which are free of allergens. Write the query the way a person would say it: 'gluten free pasta warriewood', 'nut free thai inner west', 'coeliac friendly brunch bondi', 'vegan dumplings surry hills'. Allergen, diet and place words are understood, and so are things a table needs from the venue: 'dog friendly', 'kid friendly', 'outdoor seating', 'private room for 12', 'set menu', 'group bookings', 'harbour view', 'rooftop', 'takes bookings', 'walk in only', 'baby change', 'wheelchair accessible'. Those are hard filters (all of them must hold, as on the website): only venues whose own data says yes are returned, a venue that has not said is never counted, and a party size with a private room leaves out rooms that print a smaller capacity. Each dish shows its status per allergen (free by default, or can be made free with what to ask for, such as 'GF pasta +$4'), the venue, a link, and the day the menu was read. Menus change: tell the person to confirm with the venue before ordering, especially for coeliac disease or anaphylaxis.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `eatcrush`:

```json
{
  "permissions": {
    "allow": [
      "mcp__eatcrush__search_dishes",
      "mcp__eatcrush__get_venue",
      "mcp__eatcrush__list_allergen_free",
      "mcp__eatcrush__compare"
    ],
    "ask": [],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__eatcrush__get_venue`: private-data

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-16T14:19:03.339Z, unchanged since 2026-11-16T14:19:03.339Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

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