# AudioEye Accessibility Testing (npm · @audioeye/testing-sdk-mcp)

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

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `@audioeye/testing-sdk-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-audioeye-testing-sdk-mcp/audioeye-testing-sdk-mcp.md), [page](https://verifymcp.io/servers/com-audioeye-testing-sdk-mcp/audioeye-testing-sdk-mcp)

## Channel facts

- Registry: `npm`
- Package: `@audioeye/testing-sdk-mcp`
- Version: `6.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 51 of 164 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license.
  - Actively maintained (last published 21 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1620 tokens (~101/item across 16 items; 8 tools + 8 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (50% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AudioEye Accessibility Testing MCP server?

AudioEye Accessibility Testing runs locally as an npm package, launched with npx -y @audioeye/testing-sdk-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-audioeye-testing-sdk-mcp -- npx -y @audioeye/testing-sdk-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-audioeye-testing-sdk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-audioeye-testing-sdk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-audioeye-testing-sdk-mcp -- npx -y @audioeye/testing-sdk-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-audioeye-testing-sdk-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@audioeye/testing-sdk-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-audioeye-testing-sdk-mcp --command npx --arg -y --arg @audioeye/testing-sdk-mcp
```

### Hermes

```yaml
mcp_servers:
  com-audioeye-testing-sdk-mcp:
    command: "npx"
    args: ["-y", "@audioeye/testing-sdk-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-audioeye-testing-sdk-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-audioeye-testing-sdk-mcp -t stdio -c npx -a -y @audioeye/testing-sdk-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-audioeye-testing-sdk-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@audioeye/testing-sdk-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (8)

### `audioeye_open_browser` (~92 tokens)

Launch (or focus) the AudioEye-controlled Chrome window with a persistent profile. Optionally navigate to a URL. Use this first when the user needs to authenticate before scanning — the browser stays open so the user can log in interactively, and the profile persists across MCP sessions so subsequent scans skip login. Idempotent.

Input parameters:

- `url` (string): Optional URL to navigate to after the browser is open.

### `audioeye_scan` (~546 tokens)

Run an AudioEye accessibility scan on the currently-open page (or navigate to `url` first). Returns a slim, agent-friendly structured result: a top-level summary, failures grouped by ruleCode and split into `sourceMapped` (with JSX source location) vs `unmapped` (typed by `bucket`: pageShell / nonReactDom / thirdPartyIframe / shadowDom), plus a `metadata` map containing rule descriptions and `sourceFixGuidance` for every rule that failed — read these directly, do not paraphrase or reformat the response. Pass `persistTo: ".agent/a11y-scan.json"` (or any workspace path) to have the server write the response to disk for you — do NOT re-emit the JSON via a Write tool yourself. The response includes `summaryMarkdown` — the canonical user-facing report. Present it to the user verbatim: never dump the raw JSON, never reformat or rebuild the tables, and never build an HTML page, artifact, or custom UI for scan results unless the user explicitly asks for a different format. When the user asked a pointed question, answer it directly — but any tabular summary you show must be `summaryMarkdown`, verbatim.

Input parameters:

- `forceReload` (boolean): When true, reload the page before scanning. Default: false — a matching `url` (or omitted `url`) scans the existing DOM without reloading. Use this only when the `staleMutatedDom` diagnostic told you…
- `persistTo` (string): Path to write the scan response to. Workspace-relative paths (e.g. `.agent/a11y-scan.json`) are resolved against the workspace root — `process.env.AUDIOEYE_MCP_WORKSPACE` when set, otherwise `process…
- `runOptions` (object): Partial AudioEye SDK RunOptions. Sensible defaults applied.
- `url` (string): Optional URL to navigate to before scanning. If omitted, scans the current page.
- `waitForReadyMs` (integer): Milliseconds to wait after navigation before scanning, to allow async content to render.

Output parameters:

- `componentClusters` (array)
- `currentUrl` (string)
- `failures` (array)
- `ignore` (object)
- `metadata` (object)
- `persistedTo` (string)
- `scannedAt` (string)
- `sourceMappingDiagnostics`
- `summary` (object)
- `summaryMarkdown` (string)
- `url` (string)

### `audioeye_get_rule_metadata` (~163 tokens)

Look up rule metadata (title, description, fixAtSource, sourceFixGuidance, severity, classification, wcagCriteria) for one or more ruleCodes. PREFER reading `metadata[ruleCode]` directly from the most recent `audioeye_scan` response — the scan response embeds trimmed metadata for every failed rule. Call this tool only when the agent needs metadata for a ruleCode from a *previous* scan whose response is no longer in the agent context. Every known ruleCode resolves from the built-in rule catalogue even before the first scan; scans in the current process enrich those entries. Only an unrecognized ruleCode appears in `missing`.

Input parameters:

- `ruleCodes` (array, required): Array of ruleCodes to look up. Required and non-empty.

### `audioeye_get_source_context` (~115 tokens)

Read the source code surrounding a `DebugSource` from a previous scan. Returns ±contextLines around `source.lineNumber`, the absolute file path, and the line range actually returned (clamped to file bounds). Use this before proposing a fix so your edits land in the right component — do not guess at the surrounding code.

Input parameters:

- `contextLines` (integer): Lines of context above and below the target line. Default 20.
- `source` (object, required): A `DebugSource` from a previous scan response.

Output parameters:

- `endLine` (integer)
- `filePath` (string)
- `outOfBounds` (boolean)
- `snippet` (string)
- `startLine` (integer)
- `totalLines` (integer)
- `truncated` (boolean)

### `audioeye_verify_fix` (~194 tokens)

Re-scan the page after applying a fix and report whether the targeted `(ruleCode, source.fileName, source.lineNumber)` failure is gone. Use this *immediately* after applying a fix the user approved — do not skip the verify step, and do not declare the fix landed without it. Returns `resolvedAtSource: true` when no failure within ±15 lines of the source still fails (tolerance accommodates JSX shifts from wrapping elements / prop reflow).

Input parameters:

- `ruleCode` (string, required): The ruleCode of the failure you just attempted to fix.
- `source` (object, required): The DebugSource of the failed instance you targeted in the fix.
- `url` (string): Optional URL to navigate to before re-scanning. Omit to re-scan the current page.
- `waitForReadyMs` (integer): Milliseconds to wait after navigation before scanning, to allow async content to render.

Output parameters:

- `remainingForRule` (integer)
- `remainingTotal` (integer)
- `resolvedAtSource` (boolean)
- `scannedAt` (string)
- `url` (string)

### `audioeye_get_a11y_facts` (~169 tokens)

Compute the assistive-tech facts for an element on the currently-open page: computed accessible name, computed role, resolved aria-* attributes, plus nearest-landmark and nearest-focusable-ancestor context. Use this BEFORE proposing an aria-label / role fix — an outerHTML snippet does not tell you what AT users actually hear, and the element may already be labelled by an ancestor.

Input parameters:

- `cssSelector` (string, required): CSS selector identifying the element to inspect. Prefer the `cssSelector` field on a scan failure (full, untruncated) over `cssSelectorTail` (display-truncated to 120 chars and may begin with `…`, so…

Output parameters:

- `element` (object)
- `selectorMatched` (boolean)

### `audioeye_close_browser` (~39 tokens)

Shut down the AudioEye-controlled Chrome window. The persistent profile is preserved on disk so the user does not have to log in again next session.

### `audioeye_login` (~78 tokens)

Sign in to AudioEye via browser device-pairing (no terminal needed). First call returns a portal URL and a short code to confirm there, then polls in the background and stores the SDK credentials on approval — call again to check progress. Reports signed_in / pending / expired / denied. A no-op success when credentials are already configured.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-audioeye-testing-sdk-mcp/audioeye-testing-sdk-mcp#diagnostics

## Score history

- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 74
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 64
- 2026-09-03: 49

## Common questions

### What is the AudioEye Accessibility Testing MCP server?

AudioEye Accessibility Testing is an MCP server listed in the public MCP registry as com.audioeye/testing-sdk-mcp. Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source. This page covers its npm package (@audioeye/testing-sdk-mcp).

### Is the AudioEye Accessibility Testing MCP server safe to use?

AudioEye Accessibility Testing scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the AudioEye Accessibility Testing MCP server expose?

AudioEye Accessibility Testing exposes 8 tools: audioeye_open_browser, audioeye_scan, audioeye_get_rule_metadata, audioeye_get_source_context, audioeye_verify_fix, and 3 more. Their descriptions and schemas cost roughly 1,396 tokens of context every time the server is loaded.

### Is the AudioEye Accessibility Testing MCP server still maintained?

AudioEye Accessibility Testing is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/@audioeye/testing-sdk-mcp
- Socket report: https://socket.dev/npm/package/@audioeye/testing-sdk-mcp
- Website: https://developer.audioeye.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-audioeye-testing-sdk-mcp/audioeye-testing-sdk-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-audioeye-testing-sdk-mcp/audioeye-testing-sdk-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-audioeye-testing-sdk-mcp/audioeye-testing-sdk-mcp