RatedWithAI

Check websites for WCAG issues

RatedWithAI checks a live public website for accessibility problems. Give it an address and it loads the page in a real browser, runs the axe-core WCAG 2.1/2.2 AA rules on it and on up to two more pages from the same site, and returns a 0-100 score, a letter grade and the failing rules, ordered by severity, with how many elements each affects and example markup.

What you can ask

Check my website example.com for accessibility issues.
Example path →

MCP connector

Server URL: https://ratedwithai.com/api/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: Ratedwithai runs a real WCAG 2.1/2.2 accessibility scan (axe-core in a headless browser) against a live public web page and reports the failing rules, how many elements each one affects, and example markup. Use when the user wants a website or URL checked for accessibility, ADA/WCAG/EAA compliance problems, screen-reader or keyboard barriers, or an accessibility score. Use when the user asks how to fix a specific axe rule id returned by a scan (for example color-contrast or image-alt). Do not use these tools for questions about accessibility law in general, for pages behind a login, or for local files and HTML snippets — the scanner only loads public http(s) URLs. A scan is automated: it catches roughly a third to a half of WCAG issues and is not a legal compliance certification; say so when presenting results.

Tools

Reads data2

Skills

None in the store listings or on the server

MCP connector

Server URL

https://ratedwithai.com/api/mcp

None

Protocol

MCP 2025-11-25

Instructions

Ratedwithai runs a real WCAG 2.1/2.2 accessibility scan (axe-core in a headless browser) against a live public web page and reports the failing rules, how many elements each one affects, and example markup. Use when the user wants a website or URL checked for accessibility, ADA/WCAG/EAA compliance problems, screen-reader or keyboard barriers, or an accessibility score. Use when the user asks how to fix a specific axe rule id returned by a scan (for example color-contrast or image-alt). Do not use these tools for questions about accessibility law in general, for pages behind a login, or for local files and HTML snippets — the scanner only loads public http(s) URLs. A scan is automated: it catches roughly a third to a half of WCAG issues and is not a legal compliance certification; say so when presenting results.