mcpbeat Sign in

AudioEye Accessibility Testing MCP Server

local only

AudioEye Accessibility Testing runs on your own machine — the client starts it, so there is no endpoint to ping. 31 installs a week from npm.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 149 · avg 15 · -47% w/w
a month agotoday
31
Installs / week
npm · @audioeye/testing-sdk-mcp
—
Stars
on GitHub
—
Last commit
3 releases in 90 days
—
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add testing-sdk-mcp -- npx -y @audioeye/testing-sdk-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "testing-sdk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.testing-sdk-mcp]
command = "npx"
args = ["-y", "@audioeye/testing-sdk-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "testing-sdk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "testing-sdk-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: AUDIOEYE_TESTING_SDK_CLIENT_ID (AudioEye testing-SDK license client id. Optional at startup; scans fail closed without it), AUDIOEYE_TESTING_SDK_CLIENT_TOKEN (AudioEye testing-SDK license client token. Optional at startup; scans fail closed without it), AUDIOEYE_MCP_WORKSPACE (Repo root for source-context tools and .audioeye-mcp.json discovery; defaults to the server's working directory).

Alternatives to AudioEye Accessibility Testing

same job, measured the same way
Kilotest
by jrpool

Ensemble testing of web pages for accessibility, usability, and web standards

12 tools answering
Wcag Accessibility
by aditya-ariosity

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

16 installs/wk local only
Firestore Rules Guard
by jmshinhwa

Audits firestore.rules and storage.rules for public access, expired test-mode dates and missing owne

32 installs/wk local only
ProdPoke
by prodpoke

AI QA tester — real browsers scan sites for bugs, SEO, perf, and accessibility issues via chat.

answering
OverlayQA
by overlayqa

Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.

121 installs/wk answering
Hera Fertility
by herafertility

Find male fertility testing at labs near a US ZIP code, with prices and a link to order.

3 tools answering
Validoria MCP
by validoria

Continuous website testing by Validoria — monitor security, SEO, performance, and accessibility.

15 installs/wk 74 tools answering
IsolatedTester — TinkyVision system
by agewellepm

Isolated macOS app tests, MCP images, OCR/ASCII frames, accessibility and evidence reports.

local only

AudioEye Accessibility Testing — questions

Answers built from our own checks of this server.

Why is there no uptime for AudioEye Accessibility Testing?
AudioEye Accessibility Testing runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @audioeye/testing-sdk-mcp was installed 31 times last week.
Is AudioEye Accessibility Testing still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect AudioEye Accessibility Testing?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @audioeye/testing-sdk-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use AudioEye Accessibility Testing?
The npm package @audioeye/testing-sdk-mcp was installed 31 times in the last week. Week over week that is -47%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.