tactual-mcp
OfficialRelated Servers
Alternatives to tactual-mcp
AlicenseBqualityAmaintenanceA Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.10257,629,601 npm37,580Apache 2.0
Related Servers
- AlicenseBqualityCmaintenanceEnables WCAG accessibility inspection of websites, with tools to check, analyze, and report on compliance issues.428 npmISC
- FlicenseNot gradedqualityDmaintenanceEnables automated WCAG 2.2 AA accessibility audits of Figma designs and webpages. Generates detailed markdown reports with severity-grouped violations, specific criterion references, and concrete fix recommendations.-
- AlicenseNot gradedqualityCmaintenanceVisual frontend accessibility inspector MCP server. WCAG contrast checking, touch target validation, heading hierarchy audits, responsive screenshots, and S+ grading across mobile and desktop viewports.MIT

uxlintofficial
AlicenseAqualityBmaintenanceAudits any site's UX the way a design-literate reviewer would — contrast, tap targets, type scale, colour discipline, scan patterns, copy — and returns the rule, the source line and the exact fix.6Apache 2.0- FlicenseNot gradedqualityCmaintenanceExamines web pages through screen-reader actions and speech, enabling agents to perform accessibility checks and interact with page content.-
- AlicenseNot gradedqualityDmaintenanceAutonomous WCAG 2.1 accessibility auditor that scans, fixes, re-verifies, and generates VPAT 2.5 EN 301 549 reports using AI vision analysis + DOM scanning.8,282 npm1MIT
TDQS
Scored across 9 tools
Each tool has a distinct purpose, but analyze_url, analyze_pages, trace_path, and validate_url all relate to page analysis and may initially appear overlapping. The descriptions clarify the differences, though the names alone do not make the boundaries obvious.
Most tools follow a clear verb_noun pattern (save_auth, list_profiles, analyze_url, analyze_pages, trace_path, validate_url, diff_results, suggest_remediations). However, calibration_report breaks the pattern as a noun phrase rather than an action (e.g., generate_calibration_report), creating a minor inconsistency.
Nine tools cover the accessibility analysis workflow coherently: auth setup, single/multi-page analysis, path tracing, validation, comparison, remediation suggestions, profile listing, and calibration. No obvious redundancy or bloated surface area.
The set covers the full workflow from authentication capture through analysis, trace explanation, multi-page aggregation, result comparison, remediation guidance, and model validation. Obvious gaps are not apparent for the stated purpose.