AudioEye Accessibility Testing MCP server
Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source.
C58/100grade C
Adoption
New
38 downloads/wk
Reviews
Write oneNobody has reviewed AudioEye Accessibility Testing yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
AudioEye Accessibility Testing tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
no findings
- Code scan10 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityverified namespace with website, no repo4/10
Overall 58/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @audioeye/testing-sdk-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add testing-sdk-mcp -- npx -y @audioeye/testing-sdk-mcp
AudioEye Accessibility Testing: common questions
- Is AudioEye Accessibility Testing MCP server safe?
- With care: it is graded C, so read the findings first (58/100). Read the AudioEye Accessibility Testing safety report
- How do I install AudioEye Accessibility Testing?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does AudioEye Accessibility Testing need an API key?
- Yes. The registry entry asks for
AUDIOEYE_TESTING_SDK_CLIENT_ID,AUDIOEYE_TESTING_SDK_CLIENT_TOKEN. - Is AudioEye Accessibility Testing maintained?
- The latest release is v6.1.0.