# `za.co.foodcompliance/foodcompliance-mcp` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. 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://anlyon.dev/servers/za.co.foodcompliance/foodcompliance-mcp
- JSON: https://anlyon.dev/api/v1/servers/za.co.foodcompliance/foodcompliance-mcp
- Version: 2.0.1 (active)
- Publisher: za.co.foodcompliance (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-29T17:18:28.318Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Food Compliance Agency — R638 COA & Hygiene Audits
South African R638 Certificate of Acceptability (COA) food safety compliance and audit tools.
```

Scanned 2026-10-29T17:18:32.887Z over streamable-http.

**5 tools: 3 change things and 2 only read.**

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

## Exfil surface

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

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| 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. | `mcp__foodcompliance__request_compliance_audit` |

## Findings

No check matched anything in these tool definitions.


## Changes things (3)

Creates or changes something that can be changed back. Claude Code: ask.

### `calculate_facility_hygiene_readiness`

- Nothing in its name or description says what it does, so it is counted as a write.

Description, as the server wrote it:

```untrusted-server-text
Scores a commercial food facility's physical layout and structural preparedness against R638 audit requirements, identifying critical non-conformances.
```

### `check_coa_requirements`

- The description's first verb is "evaluate": a word for a change.

Description, as the server wrote it:

```untrusted-server-text
Evaluates Certificate of Acceptability (CoA) statutory requirements under Regulation R638 for a specific food premises category (restaurant, butchery, bakery, cloud kitchen, food truck, warehouse, packaging plant, mobile cart).
```

### `request_compliance_audit`

- The name "request_compliance_audit" says "request": a word for a change.
- Tag outbound: The input takes a destination (input.phone): what the tool writes goes there.

Description, as the server wrote it:

```untrusted-server-text
Submits an on-site Certificate of Acceptability (CoA) pre-audit or municipal licensing inquiry directly to the Food Compliance Agency consulting desk.
```

## Only reads (2)

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

### `get_food_handler_training_standards`

- The name "get_food_handler_training_standards" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Returns statutory training mandates under Regulation R638 Regulation 3, including syllabus prerequisites, certificate validity, and Person in Charge (PIC) obligations.
```

### `get_municipal_health_guidelines`

- The name "get_municipal_health_guidelines" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Returns Environmental Health Practitioner (EHP) inspection protocols, zoning prerequisites, and submission steps for South African metropolitan municipalities.
```

## Claude Code permissions

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

```json
{
  "permissions": {
    "allow": [
      "mcp__foodcompliance__get_municipal_health_guidelines",
      "mcp__foodcompliance__get_food_handler_training_standards"
    ],
    "ask": [
      "mcp__foodcompliance__check_coa_requirements",
      "mcp__foodcompliance__calculate_facility_hygiene_readiness",
      "mcp__foodcompliance__request_compliance_audit"
    ],
    "deny": []
  }
}
```

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

- `mcp__foodcompliance__request_compliance_audit`: outbound