Scored across 16 tools
Most tools are clearly scoped to distinct resources and actions: scan_url/scan_site, check_pdf, run_journey, and verify_fix each have their own dedicated polling tool. The many get_* tools could be confused at a glance, but descriptions explicitly cross-reference which poller to use for each job type.
All tools follow a consistent lowercase snake_case verb_noun pattern (scan_url, list_sites, get_run_findings, verify_fix). Paired queue/poll tools are predictably named (check_pdf -> get_pdf_check, run_journey -> get_journey_run), making the set easy to navigate.
16 tools is slightly above the ideal 3-15 range but each tool maps to a distinct stage in the scanning pipeline: initiating a job, polling it, retrieving findings, and listing supporting resources. The count feels justified by the breadth of scan types rather than redundant.
The surface covers the core lifecycle for URL scans, full-site runs, PDF checks, journeys, trend history, and fix verification. Minor gaps exist — no site registration/update/delete and no cancellation or re-run operations — but these are likely managed outside the MCP and don't block primary workflows.