Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AudioEye Accessibility Testing

NPM · @AUDIOEYE/TESTING-SDK-MCP

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

0 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 46% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 50 of 166 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 49 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1999 tokens (~117/item across 17 items; 9 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 6 Nov 26 +1
    • Stability: fail → pass ▲ security
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@audioeye/testing-sdk-mcp@6.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 166 packages
Packages resolved 166
Stale 50
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,775 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audioeye_close_browser ~39

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

audioeye_get_a11y_facts ~201

Compute the assistive-tech facts for an element in the session's tab: computed accessible name (always a string; "" means the tree computed no name), computed role, resolved aria-* attributes, plus nearest-landmark and nearest-focusable-ancestor context (each present only when such an ancestor exists; the element itself is never its own focusable ancestor). 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.

NameTypeReqDescription
cssSelectorstringyesCSS 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…
NameTypeReqDescription
elementobject––
selectorMatchedbooleanyes–

No examples provided.

audioeye_get_rule_metadata ~145

Look up rule metadata (title, description, fixAtSource, sourceFixGuidance, severity, classification, wcagCriteria) for one or more ruleCodes. The saved scan JSON linked from each `audioeye_scan` report embeds trimmed metadata for every failed rule under `metadata[ruleCode]`; call this tool when that file is not at hand or its guidance was truncated. 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`.

NameTypeReqDescription
ruleCodesarrayyesArray of ruleCodes to look up. Required and non-empty.

No output schema declared.

No examples provided.

audioeye_get_source_context ~144

Read the source code surrounding a `DebugSource` from a previous scan. Returns ±contextLines around `source.lineNumber`, the absolute file path, the line range actually returned (clamped to file bounds), and `resolvedRoot`, the checkout holding the file. A source that lives in a checkout outside the workspace is refused with an error naming that checkout. Use this before proposing a fix so your edits land in the right component — do not guess at the surrounding code.

NameTypeReqDescription
contextLinesinteger–Lines of context above and below the target line. Default 20.
sourceobjectyesA `DebugSource` from a previous scan response.
NameTypeReqDescription
endLineintegeryes–
filePathstringyes–
outOfBoundsbooleanyes–
resolvedRootstringyes–
snippetstringyes–
startLineintegeryes–
totalLinesintegeryes–
truncatedbooleanyes–

No examples provided.

audioeye_inspect ~140

Select a component in the AudioEye inspector panel on the last scanned page: scrolls its `instance` (0-based, default 0) into view, outlines it on the page, highlights it in Chrome DevTools and opens the panel on that component. Use it to show the user "that button" without them touching the panel. Requires a scan with the inspector mounted; `componentKey` comes from `componentClusters` in the latest saved scan JSON.

NameTypeReqDescription
componentKeystringyes`componentKey` of a component from the latest saved scan JSON.
instanceinteger–0-based instance index; default 0.

No output schema declared.

No examples provided.

audioeye_login ~88

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. Re-validates stored credentials on every call and starts a new sign-in when they no longer work.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

audioeye_open_browser ~88

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.

NameTypeReqDescription
urlstring–Optional URL to navigate to after the browser is open.

No output schema declared.

No examples provided.

audioeye_scan ~644

Run an AudioEye accessibility scan on the session's tab (or navigate it to `url` first). Returns the scan report as Markdown: failure counts and tables of failures by rule, with source links and selectors. Every report is also saved to `.agent/a11y-scans/<session>/scan-<n>.md` and the result always links it; a report too long for the chat is replaced by a short header with that link. Every scan is saved in full to `scan-<n>.json` beside it, and the result always links that file too: read it for component keys, file paths, rule metadata and `sourceFixGuidance`. Do NOT re-emit the scan via a Write tool yourself. Present it to the user verbatim: 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 this report, verbatim. Keep the Source cells as the links given: IDE hosts open the file at that line; in a terminal the absolute `filePath` in the linked scan JSON, present only when the source resolved to a workspace file, is Cmd+clickable.

NameTypeReqDescription
forceReloadboolean–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…
inspectorboolean–Overrides the `inspector` config key for this scan: `false` skips injecting the in-page inspector panel, `true` forces it in any headful Chrome (the panel goes only in the tab this session opened); h…
runOptionsobject–Partial AudioEye SDK RunOptions. Sensible defaults applied.
urlstring–Optional URL to load in the session's tab before scanning. If omitted, scans the session's tab as is.
viewportobject–CSS-pixel viewport to set on the scanned tab before navigating and scanning, e.g. `{ width: 390, height: 844 }`. It stays on that tab for later scans.
waitForReadyMsinteger–Maximum milliseconds to wait for the page before scanning (default 5000); a cap, not a fixed delay. The scan starts sooner, once the body shows text or media and no network request has been in flight…

No output schema declared.

No examples provided.

audioeye_verify_fix ~286

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).

NameTypeReqDescription
ruleCodestringyesThe ruleCode of the failure you just attempted to fix.
sourceobjectyesThe DebugSource of the failed instance you targeted in the fix.
urlstring–Optional URL to load in the session's tab before re-scanning. Omit to re-scan the session's tab.
viewportobject–CSS-pixel viewport to set on the scanned tab before navigating and scanning, e.g. `{ width: 390, height: 844 }`. It stays on that tab for later scans.
waitForReadyMsinteger–Maximum milliseconds to wait for the page before scanning (default 5000); a cap, not a fixed delay. The scan starts sooner, once the body shows text or media and no network request has been in flight…
NameTypeReqDescription
remainingForRuleintegeryes–
remainingTotalintegeryes–
resolvedAtSourcebooleanyes–
scannedAtstringyes–
urlstringyes–

No examples provided.

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.

npm · @audioeye/testing-sdk-mcp

# add to Claude Code
claude mcp add com-audioeye-testing-sdk-mcp -- npx -y @audioeye/testing-sdk-mcp
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 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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 9 tools: audioeye_open_browser, audioeye_scan, audioeye_inspect, audioeye_get_rule_metadata, audioeye_get_source_context, and 4 more. Their descriptions and schemas cost roughly 1,775 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AudioEye Accessibility Testing MCP server?

VerifyMCP ran 14 checks on AudioEye Accessibility Testing, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about AudioEye Accessibility Testing: License and Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.