Site

uk.co.fireriskquotesPublished by fireriskquotes.co.ukOfficial publisherv1.0.1Updated Nov 8, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Lets an assistant describe, fill in and submit a Fire Risk Quotes enquiry, handing the person's details to human fire risk assessment providers.

What you can do
  • Read what submitting an enquiry does, who receives the details, the consent wording and how confirmation works
  • List every enquiry field with its key, label, type, required flag, help text and allowed options
  • Submit an enquiry with answers keyed by field key plus consent, returning a summary, the consent line and a confirmation token
When to use it
Use it when someone wants to request fire risk assessment quotes from UK providers and is happy to hand their details to human providers, rather than buy or get an instant quote.
Requirements
A remote streamable HTTP endpoint at fireriskquotes.co.uk; no authentication, environment variables or headers are declared.
Before you install
Submitting sends the person's enquiry details to third-party human providers, so show them the summary and consent line first. It is not a purchase or a guaranteed quote, and the confirmation token step should be completed as described.

Installation

In SourceWeft

  1. Open Site in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/uk.co.fireriskquotes%2Fsite/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "site": {
      "type": "http",
      "url": "https://fireriskquotes.co.uk/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

enquiry_describe

What you get: an ENQUIRY with a human (not a purchase, not a guaranteed quote)

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.

Takes no parameters.

enquiry_fields

The questions the enquiry asks

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.

Takes no parameters.

submit_enquiry

Submit an ENQUIRY to human providers (two steps; not a purchase)

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

Parametersanswersrequiredconsentrequiredconfirmation

Version history

2
  1. v1.0.1LatestOct 3, 2026
  2. v1.0.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.