mcpbeat Sign in

Site MCP Server

by co-fireriskquotes Your server? Claim it
answering

Site is answering right now. Last checked 15 min ago. It exposes 3 tools.

Fire Risk Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

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

Uptime history 50 days of history · worst day 94%
50 days agonow
98.9%
Uptime 24h
90 of 91 checks
3
Tools
read from the server
721 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 October 2026. No other catalogue keeps this.

8 Oct a tool description was rewritten submit_enquiry
8 Oct a tool changed the parameters it asks for submit_enquiry

Site missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 15 min ago.

run in your terminal
claude mcp add site --transport http https://fireriskquotes.co.uk/mcp
Settings → Connectors → Add custom connector, then paste this address
https://fireriskquotes.co.uk/mcp
~/.codex/config.toml
[mcp_servers.site]
url = "https://fireriskquotes.co.uk/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "site": {
      "url": "https://fireriskquotes.co.uk/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "site": {
      "type": "http",
      "url": "https://fireriskquotes.co.uk/mcp"
    }
  }
}

Available tools 3

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

enquiry
enquiry_describe
Read first. States plainly what submit_enquiry does on Fire Risk Quotes: 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 Fire Risk Quotes 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 Fire Risk Quotes — 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: "Send my contact details to up to three relevant fire risk assessors, chosen by Fire Risk Quotes, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Endpoints

URLTransportStateLatencyChecked
https://fireriskquotes.co.uk/mcp streamable-http answering 489 ms 15 min ago

Alternatives to Site

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

Washroom Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by skitransferquotes

Ski Transfer Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-demolitionquotes

Demolition Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-partywallquotes

Party Wall Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-machineryrepairquotes

Machinery Repair Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-gearboxrepairquotes

Gearbox Repair Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering
Site
by co-bngquotes

BNG Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a purchase);...

3 tools answering
Site
by co-asbestossurveyquotes

Asbestos Survey Quotes: the site's own MCP server — enquiry (enquiry = a human handoff, not a...

3 tools answering

Site — questions

Answers built from our own checks of this server.

What can Site do?
It exposes 3 tools, read directly from the server on our last check. Among them: 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 →
Is Site working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 721 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 in the form 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 3 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 721 ms on average, which is faster than 15% 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.