RatedWithAI accessibility checker
Server Details
Scan a live web page for WCAG 2.1/2.2 AA issues with axe-core: score, grade, failing rules.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools are cleanly split along an explain-vs-scan axis, and each description explicitly states when NOT to use it (explain tool refuses to scan; scan tool refuses login/localhost/pasted HTML). An agent cannot plausibly confuse them.
Both names follow a consistent verb_noun snake_case pattern (explain_accessibility_issue, scan_accessibility). The noun phrase differs in granularity but the verb-first convention is uniform.
Two tools is on the thin side for a server whose domain (accessibility checking) naturally includes rule listing, HTML-snippet scanning, or remediation planning. It is defensible as a minimal surface, but feels under-built rather than well-scoped.
Core loop of scan -> understand failure is covered, but there are notable gaps: no way to check pasted HTML, localhost, or authenticated pages (explicitly dead ends), and no tool to list supported rules or summarize a full remediation plan.
Available Tools
2 toolsexplain_accessibility_issueExplain how to fix an accessibility ruleARead-onlyIdempotentInspect
Use this when the user asks what an axe-core accessibility rule means or how to fix it — such as color-contrast, image-alt, label or link-name. Returns plain-English steps and a code example. Do not use it when the user wants a site checked; it explains a rule and does not scan pages.
Inputs: rule_id (required). Returns: known, steps, ruleId, summary, +2 more
scan_accessibilityScan a website for accessibility issuesARead-onlyIdempotentInspect
Use this when the user wants a public website or web page checked for accessibility (WCAG 2.1/2.2 AA, ADA, EAA, Section 508): it loads the live page in a real browser, runs axe-core on it and up to two more same-site pages, and returns a 0-100 score, a letter grade and the failing rules with example elements. Takes 15-40 seconds. Do not use it for pages that need a login, for localhost or private-network addresses, or for pasted HTML.
Inputs: url (required). Returns: url, grade, score, scannedAt, +7 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Scan URLs or HTML for WCAG 2.2 violations. 75-rule manifest, weighted score, shareable reports.
Scan a web page for accessibility, security, privacy, quality and SEO issues, with fixes.
Run WCAG accessibility scans on websites, list each issue with its element, and triage from chat.
Deterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account.
Related MCP Servers
- AlicenseAqualityBmaintenanceChecks a website or local dev server with axe-core (WCAG 2.0/2.1 A and AA) and returns a fix prompt with real examples from the pages, for the AI tool to fix the source. Automated checks find roughly a third of accessibility problems.1153 npmMIT
- AlicenseBqualityDmaintenanceAudits web pages for WCAG 2.2 AA accessibility aligned with the GOV.UK standard using axe-core and headless Chromium, returning structured JSON, markdown reports, and GDS compliance summaries.441MIT
- AlicenseAqualityBmaintenanceScans live web pages and single-page apps across multiple viewports to detect WCAG 2.1 AA accessibility violations and returns concrete, browser-verified fixes grounded in WCAG success criteria and techniques.575 npm2MIT
- AlicenseAqualityDmaintenanceEnables web accessibility audits using axe-core, allowing users to scan URLs, check WCAG compliance levels, and export reports. It uses an anti-detect browser to bypass Cloudflare and other bot protection.749 PyPIMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.