AccessLens MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESSLENS_ALLOW_PRIVATE_TARGETS | No | Set to 'true' to allow localhost/private-network targets. By default only http(s) URLs are accepted and localhost/private-network targets are blocked. | false |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crawl_accessibility_reviewA | Crawl ordinary same-origin anchor links breadth-first from a start URL, within explicit page/depth limits. Runs the same Playwright, axe-core, QualWeb, structural, and advisory review on every discovered page, then returns one combined pending-human-review report. External links and unlinked SPA routes are not guessed. |
| run_accessibility_reviewA | Preferred one-call workflow. Render a URL or HTML once with Playwright; run axe-core, AccessLens structural/session checks, QualWeb ACT Rules when an URL is supplied, and static reading-order, alt-text, control-name, and keyboard advisories. Returns one human-review report. Do not edit code; present the report and wait for explicit approval. |
| analyze_accessibility_evidenceA | Render a URL or HTML document, run axe-core plus AccessLens semantic checks (and QualWeb ACT Rules for URL scans), preserve raw per-engine provenance, and persist a pending-human-review report. Do not modify code: present get_review_report to the human first. |
| get_review_reportC | Create the human-facing review packet: each open finding, evidence, proposed safe remediation category, and its approval status. An agent must show this report and ask for explicit human approval before editing code. |
| record_human_reviewA | Record an explicit human decision after the human has reviewed the report. Only call this tool in response to a clear human approval or rejection; it is not permission for the agent to decide on its own. |
| verify_fixA | Re-scan a fixed page and determine whether a previously observed finding cleared. This tool rejects verification unless that finding has a recorded human approval. Also reports new rules introduced since the original scan. |
| check_session_consistencyC | Review stored page snapshots for duplicate IDs, heading-level gaps, multiple main landmarks, and controls whose stable DOM path acquired a different accessible name across scans. |
| get_session_reportB | Return all recorded verification outcomes, the verified-fix-rate, current open findings, and scan totals. |
| analyze_reading_orderB | Advisory check: compare focus/tab order with rendered bounding-box order. It is not a substitute for a human reading-order assessment. |
| analyze_alt_textB | Advisory check for missing or generic alt text. It cannot assess semantic truthfulness without a vision model. |
| analyze_control_namesC | Advisory inventory of repeated control names and roles for human review. |
| analyze_keyboard_pathsB | Advisory static keyboard reachability check. It does not simulate full interaction flows. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
run_accessibility_review, analyze_accessibility_evidence, and crawl_accessibility_review all trigger overlapping accessibility scans, and crawl is mainly differentiated by multi-page breadth. The descriptions help clarify intent, especially with 'Preferred one-call workflow' on run_accessibility_review, but several advisory tools also duplicate checks already included in the main review.
Every tool uses a consistent lowercase snake_case verb_noun pattern: crawl_, run_, analyze_, get_, record_, verify_, and check_. Report, session, review, and fix nouns are used predictably, making the set highly navigable.
Twelve tools is within a reasonable range for an accessibility audit server, but the count feels slightly padded by overlapping review entry points and standalone advisory checks that duplicate capabilities already present in run_accessibility_review. Consolidation would make the set tighter without losing coverage.
The scan-to-report-to-human-approval-to-verification lifecycle is well covered, with crawl, session consistency, and aggregate reporting adding useful breadth. Minor gaps like explicit session management or scan-scope configuration exist, but the core workflow has no dead ends.