_ registry / mcp + a2a streamable-http · checked 2h ago

food-compliance-agency-mcp

https://foodcompliance.co.za

Registry code: 2dce8912f90b111e

api record

South African R638 Certificate of Acceptability (COA) food safety compliance and audit tools.

from a public catalogue that lists it, not from the operator

endpoint
https://foodcompliance.co.za/mcp
door code
c144a5ddb9133ccb
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is food-compliance-agency-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is food-compliance-agency-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does food-compliance-agency-mcp have?
5 tools: calculate_facility_hygiene_readiness, request_compliance_audit, get_food_handler_training_standards, get_municipal_health_guidelines, check_coa_requirements.
Is food-compliance-agency-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
219ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_food_handler_training_standards open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "role": {
          "enum": [
            "person_in_charge",
            "food_handler",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "Role or level of training."
        }
      }
    }
    arguments 15 lines
  • get_municipal_health_guidelines open 2h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "municipality": {
          "enum": [
            "City of Tshwane",
            "City of Johannesburg",
            "Ekurhuleni",
            "City of Cape Town",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "Target municipal area."
        }
      }
    }
    arguments 17 lines
  • check_coa_requirements open 2h ago

    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).

    mcp-tool

    {
      "type": "object",
      "required": [
        "premises_type"
      ],
      "properties": {
        "municipality": {
          "enum": [
            "City of Tshwane",
            "City of Johannesburg",
            "Ekurhuleni",
            "City of Cape Town",
            "Other"
          ],
          "type": "string",
          "default": "City of Tshwane",
          "description": "Governing municipal health jurisdiction."
        },
        "premises_type": {
          "enum": [
            "restaurant_cafe",
            "butchery",
            "bakery",
            "cloud_kitchen",
            "food_truck",
            "warehouse_distribution",
            "food_manufacturing",
            "mobile_cart"
          ],
          "type": "string",
          "description": "Category of food establishment."
        }
      }
    }
    arguments 34 lines
  • calculate_facility_hygiene_readiness unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "has_dedicated_handwash_basin",
        "has_double_compartment_sink",
        "walls_impervious_tiled",
        "floors_smooth_coved"
      ],
      "properties": {
        "has_grease_trap": {
          "type": "boolean",
          "description": "Functional vented fat trap on wash basins."
        },
        "floors_smooth_coved": {
          "type": "boolean",
          "description": "Impervious, non-slip flooring with coved rounded skirting."
        },
        "pest_control_contract": {
          "type": "boolean",
          "description": "Active pest management service contract and bait stations."
        },
        "has_separate_prep_sink": {
          "type": "boolean",
          "description": "Dedicated sink for vegetable or raw meat preparation."
        },
        "walls_impervious_tiled": {
          "type": "boolean",
          "description": "Light-colored washable tiled or epoxy walls up to min 1.8m."
        },
        "trained_person_in_charge": {
          "type": "boolean",
          "description": "Certified PIC under Regulation R638."
        },
        "has_double_compartment_sink": {
          "type": "boolean",
          "description": "Dual pot sink with hot water for sanitizing."
        },
        "has_dedicated_handwash_basin": {
          "type": "boolean",
          "description": "Dedicated basin with liquid soap and disposable paper towels."
        }
      }
    }
    arguments 43 lines
  • request_compliance_audit unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "business_name",
        "contact_person",
        "phone",
        "premises_type",
        "location_city"
      ],
      "properties": {
        "email": {
          "type": "string"
        },
        "phone": {
          "type": "string"
        },
        "urgent": {
          "type": "boolean",
          "default": false
        },
        "business_name": {
          "type": "string"
        },
        "location_city": {
          "type": "string"
        },
        "premises_type": {
          "type": "string"
        },
        "contact_person": {
          "type": "string"
        }
      }
    }
    arguments 34 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2dce8912f90b111e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2dce8912f90b111e/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2dce8912f90b111e/badge.svg)](https://brick.blue/agent/2dce8912f90b111e?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
195ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.