IDV Deadline: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
Scored across 6 tools
The set splits cleanly into two families: checker_* for the decision guide and enquiry_* for the submission flow, so the two domains are distinguishable. Within the checker group, checker_start and checker_tree both surface questions, which can be mildly confused, but the descriptions (interactive step vs. full dump) clarify the difference.
The checker_* group (checker_start, checker_answer, checker_tree) is consistent, as is the enquiry_* pair (enquiry_describe, enquiry_fields). However submit_enquiry breaks the prefix_noun pattern with a verb_noun form, mixing conventions even if all are lowercase snake_case and still readable.
Six tools is well-scoped for a decision-guide plus enquiry site. Each tool earns its place: three for the checker flow and three for the enquiry flow, with no redundant or filler entries.
Both workflows appear fully covered: start/answer/tree for the checker and describe/fields/submit for the enquiry, including a two-step consent confirmation. Minor gap: no standalone way to fetch a verdict or resume state outside checker_answer, but the core lifecycle is intact.
Given a question id and the chosen option (its choice index), return the next question or the final verdict.
Inputs: choice (required), question (required).
The first question of the Identity verification deadline checker decision guide.
Inputs: no named parameters.
Every question, option and verdict of the Identity verification deadline checker guide, for reasoning end to end.
Inputs: no named parameters.
Read first. States plainly what submit_enquiry does on IDV Deadline: 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.
Inputs: no named parameters.
Every field of the IDV Deadline 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.
Inputs: no named parameters.
Submits an enquiry to IDV Deadline — 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 accountancy and tax firms, chosen by IDV Deadline, 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."
Inputs: answers (required), consent (required), confirmation.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Revalidation Tracker: the site's own MCP server — checker, enquiry (enquiry = a human handoff,...
Eligible By Descent: the site's own MCP server — checker, enquiry (enquiry = a human handoff,...
P11D Changes: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
Drone Licence Checker: the site's own MCP server — checker, enquiry (enquiry = a human handoff,...
Add one secure layer between your agents and this server.
