Skip to main content
Glama
allchemylabs

@allchemylabs/aether-wcag-scanner

Official
by allchemylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ALLCHEMY_API_KEYNoYour Allchemy Labs API key. Optional; without it the scanner still works but returns template-based fixes instead of corpus-grounded ones.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
aether_scan_and_fixA

Scan a URL (or a multi-route SPA via the spa block) for WCAG 2.1 AA accessibility violations AND generate RAG-powered fixes in one call. Returns violations paired with fixHtml, explanations, and WCAG technique references. Set maxFixes:0 for a fast scan-only pass. This is the recommended tool for accessibility auditing — use it when a developer asks to check or fix accessibility.

aether_get_fixA

Get a RAG-powered fix OR explanation for a WCAG violation. Pass html (the failing element) to get a concrete fixHtml plus a measured verification. Omit html to get a rule-level explanation (WCAG success criteria, technique code examples, failure patterns, and fix guidance). Requires ALLCHEMY_API_KEY for RAG output; falls back to templates without it.

aether_check_htmlA

Analyze an HTML snippet for WCAG accessibility issues without needing a live URL or browser. Uses static heuristic checks and optionally enriches results with RAG-powered fixes. Use this when a developer pastes HTML or asks about a component's accessibility.

aether_verify_fixA

Deterministically verify a WCAG fix with the real Playwright + axe-core engine. URL mode re-scans a live page; snippet mode diffs original vs fixed HTML before deploy. Returns MEASURED facts: targetCleared, newViolations (regressions), resolvedViolations, and complianceDelta. This is the authoritative "did the fix work?" signal.

aether_submit_feedbackA

Submit developer feedback on a previously returned WCAG fix/artifact, keyed by its finding_id. Records a rating plus an optional reason_code and the code the developer actually shipped, so the fix pipeline can learn from misses. Requires ALLCHEMY_API_KEY.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool addresses a distinct phase of the accessibility workflow: analyzing static HTML, scanning/fixing a URL, retrieving fixes/explanations, verifying fixes, and submitting feedback. There is no overlap or ambiguity between their purposes.

Naming Consistency4/5

All tools share the 'aether_' prefix and mostly follow a verb_noun pattern (check_html, get_fix, verify_fix, submit_feedback). The exception is 'scan_and_fix', which uses a compound verb phrase, but this is still clear and consistent in style.

Tool Count5/5

With 5 tools, the server covers the full lifecycle of accessibility auditing and remediation without bloat. Each tool is necessary and earns its place, making the count well-scoped for the domain.

Completeness5/5

The tool surface covers analysis, scanning with optional fixes, retrieval of detailed fix guidance, verification of applied fixes, and feedback collection. There are no obvious missing operations for the intended workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources