mcpbeat Sign in

Site MCP Server

by co-foodhygienealerts Your server? Claim it
answering

Site is answering right now. Last checked 12 min ago. It exposes 6 tools.

Food Hygiene Alerts: the site's own MCP server — checker, enquiry (enquiry = a human handoff,...

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 4 days of history
4 days agonow
100.0%
Uptime 24h
92 of 92 checks
6
Tools
read from the server
597 ms
Response time
average over 24h
open, no key
Access
streamable-http

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add site --transport http https://foodhygienealerts.co.uk/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "site": {
      "url": "https://foodhygienealerts.co.uk/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.site]
url = "https://foodhygienealerts.co.uk/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "site": {
      "url": "https://foodhygienealerts.co.uk/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "site": {
      "url": "https://foodhygienealerts.co.uk/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

checker
checker_answer
Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.
checker_start
The first question of the Which food hygiene position are you in? decision guide.
checker_tree
Every question, option and verdict of the Which food hygiene position are you in? guide, for reasoning end to end.
enquiry
enquiry_describe
Read first. States plainly what submit_enquiry does on Food Hygiene Alerts: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
enquiry_fields
Every field of the Food Hygiene Alerts enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
submit
submit_enquiry
Submits an enquiry to Food Hygiene Alerts — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to food safety consultants, who'll contact me directly."

Endpoints

URLTransportStateLatencyChecked
https://foodhygienealerts.co.uk/mcp streamable-http answering 238 ms 12 min ago

Alternatives to Site

same job, measured the same way
Site
by co-temperaturelog

Temperature Log: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...

6 tools answering
Blackpoint Cyber
by wyre-ai

MCP server for Blackpoint Cyber MDR — alerts, threats, and operations.

local only
Blackpoint Cyber
by wyre-technology

MCP server for Blackpoint Cyber MDR — alerts, threats, and operations.

local only
Datto RMM
by wyre-technology

MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.

local only
Datto RMM
by wyre-ai

MCP server for Datto RMM — devices, alerts, sites, jobs, and audit data.

local only
NinjaOne
by wyre-ai

MCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.

local only
NinjaOne
by wyre-technology

MCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.

local only
RocketCyber
by wyre-ai

MCP server for RocketCyber Managed SOC — incidents, alerts, agents, and customer telemetry.

local only

Site — questions

Answers built from our own checks of this server.

What can Site do?
It exposes 6 tools, read directly from the server on our last check. Among them: checker_answer, checker_start, checker_tree, enquiry_describe, enquiry_fields, submit_enquiry. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Site mostly used for?
Its tools cluster around checker and enquiry. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Site working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 597 ms. The bar chart above shows every period we have measured.
Is Site still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Site?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Site need an API key?
No. Site completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Site?
It answers our handshake in 597 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.