site
SAR Builder: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
- 1.0.1
- Version
- remote
- Transport
- 6
- Tools
Security review
Review passedReviewed 1d ago.
- tools: 6 tools scanned
- metadata: scanned
No findings.
Tools (6)
checker_start
The first question of the Subject access request builder decision guide.
checker_answer
Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.
checker_tree
Every question, option and verdict of the Subject access request builder guide, for reasoning end to end.
enquiry_describe
Read first. States plainly what submit_enquiry does on SAR Builder: 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 SAR Builder 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_enquiry
Submits an enquiry to SAR Builder — 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 solicitors, chosen by SAR Builder, 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."