No user-submitted related servers found.
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. The tool's purpose (run a WCAG accessibility audit via axe-core in a real browser) is unambiguous and clearly stated.
With a single tool, naming is trivially consistent. The name audit_wcag_accessibility follows a clear verb_noun/domain-noun convention that is readable and descriptive.
One tool is borderline thin for a server with this much surface area (single vs. batch domains, multiple presence checks, scoring, EAA signals). It works as a single 'do the audit' entry point, but the lack of any companion tool makes the surface feel under-provisioned.
The audit itself is well-covered, including error rows for blocked/unreachable sites. However, there is no tool to retrieve or re-fetch results for a run ID (which the description says is returned on failure), and no way to list past runs or fetch detailed per-element remediation data, creating a dead end after errors.
