AudioEye Accessibility Testing — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Browser accessibility scan and JSX issue mapping MCP

What we know

Browser accessibility scan and JSX issue mapping MCP. Published by the owner of npm package @audioeye/testing-sdk-mcp. Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source.

Maintenance / activity evidence

512 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally. Reported action classes: Write persisted scan outputs; Open browser. Complete write authority is not verified.
AudioEye device browser login / SDK entitlement
Sensitive access: Service account information and data accessible by supplied credentials

Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 512 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @audioeye/testing-sdk-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has @audioeye/testing-sdk-mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.

Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
AudioEye device browser login / SDK entitlement
Reviewed write actions: Write persisted scan outputs; Open browser
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

512 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/@audioeye/testing-sdk-mcp

Exact implementation source: https://www.npmjs.com/package/@audioeye/testing-sdk-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@audioeye/testing-sdk-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
@audioeye/testing-sdk-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
MCP100 setup guide
Publisher MCP is public npm, Node 22+ required (except bundled Claude Desktop MCPB). Browser device-pair licensing; private npm registry credentials for other AudioEye SDK packages are not required for MCP distribution.
client registration · Claude Code only · Publisher instructions
claude mcp add audioeye --scope user -- npx --prefix / -y @audioeye/testing-sdk-mcp@latest
reviewed install or registration · MCP100 composed guide
npx -y @audioeye/testing-sdk-mcp@latest setup
Configure / authenticate
MCP100 setup guide
Requires Node >=22 and AudioEye account with Testing SDK license for scans. `setup` registers on detected hosts. `npx -y @audioeye/testing-sdk-mcp@latest login` authenticates; bare package startup may only expose rule lookup.
Check connection
Publisher instructions
`npx -y @audioeye/testing-sdk-mcp@latest whoami` checks login; inspect tools. Do not run billable/consuming scans.
read only whoami · Publisher instructions
npx -y @audioeye/testing-sdk-mcp@latest whoami
Remove / uninstall / revoke
MCP100 setup guide
Remove the `audioeye` MCP registration in each configured host (Claude Code: `claude mcp remove audioeye` if same name). If authenticated with CLI, `npx -y @audioeye/testing-sdk-mcp@latest logout` removes local saved sign-in. Do not treat logout as client unregistration.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Separate credential guidance (provider revocation is not verified): Official AudioEye MCP docs verify local logout; separate organization-level license/token revocation requires AudioEye account administration and is not claimed by logout.
local session logout · Publisher instructions
npx -y @audioeye/testing-sdk-mcp@latest logout

Official Documentation & Sources

What it does

Browser accessibility scan and JSX issue mapping MCP. Published by the owner of npm package @audioeye/testing-sdk-mcp. Scans live pages with the AudioEye rules engine and maps accessibility issues to JSX source.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Browser accessibility scan and JSX issue mapping MCP

Representative uses

Browser accessibility scan and JSX issue mapping MCP

Limitations

Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: AudioEye device browser login / SDK entitlement
Permissions: Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.
Data handling: Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.

Access scope and cautions

Write actions: Not verified Write persisted scan outputs Open browser
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: medium
Security notes: Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: AudioEye device browser login / SDK entitlement

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Write persisted scan outputs; Open browser. Recorded permission context: Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally.

What data-handling boundary should I consider?

Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

Licenced browser scan requires AudioEye credentials and a persistent Chrome profile; scans may traverse live pages and persist findings locally. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.