MCP.Market

AudioEye Accessibility Testing MCP server

by audioeye.com·com.audioeye/testing-sdk-mcp·v6.2.0

Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source.

C58/100grade C
What users say
No reviews yet
Be the first
Safety scan
C58/100

full report

Adoption
New

73 downloads/wk

Reviews

Write one

Nobody 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.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 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

How AudioEye Accessibility Testing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
58/100
higher than 13% of 48,243 servers
Downloads a week
73
more than 54% of 12,306 servers with a package

Release history: 2 versions in the registry since 2026-09-03, latest 2026-10-02, typically one every 29 days.

Install AudioEye Accessibility Testing in Claude Code, Cursor or VS Code

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
Add to Cursor

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, Cursor, VS Code or Claude Desktop 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.2.0.
What can I use instead of AudioEye Accessibility Testing?
Servers from other publishers that do the same job: Front-End Checklist MCP server.
How does AudioEye Accessibility Testing compare with other MCP servers?
safety score 58/100 (higher than 13% of 48,243 servers); downloads a week 73 (more than 54% of 12,306 servers with a package). Full comparison.

Alternatives to AudioEye Accessibility Testing

Same job from other publishers: the closest match first, then the best rated.

  • Front-End Checklist
    Review frontend code and live pages against 386 quality-gated web development rules.
    A