Lazynext Accessibility Checker MCP server
online · 100% uptimecom.lazynext/accessibility-checker·v1.0.0Scan URLs or HTML for WCAG 2.2 violations. 75-rule manifest, weighted score, shareable reports.
0 stars
Reviews
Write oneNobody has reviewed Lazynext Accessibility Checker yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Lazynext Accessibility Checker tools (4)
write = sends, deletes, buys or postsget_reportFreeFetch a stored scan report by its id (from a prior scan_url/scan_html result).
list_rulesFreeList every WCAG criterion the scanner can emit, with level and detection path.
scan_htmlFreeAudit pasted HTML markup for WCAG violations (static rules — no render, no quota).
scan_urlFreeRender and audit a live web page for WCAG 2.1/2.2 violations. Returns score, findings, and a shareable report URL. Free tier: 3 URL scans/day/IP; pass a Pro license email for more.
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 525ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How Lazynext Accessibility Checker compares
Against every graded Security MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 90% of 915 Security servers
- Tools
- 4
- the typical Security server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Security server answers 100%
- Response time
- 49 ms
- faster than 95% of 547 Security servers
What its tools let an agent do: 4 read
Install Lazynext Accessibility Checker in Claude Code, Cursor or VS Code
claude mcp add --transport http accessibility-checker https://api.lazynext.com/mcp
What the publisher says
From the Lazynext Accessibility Checker repository's README, as published. We do not edit it. Read it on GitHub
Accessibility Checker
Real WCAG 2.1 accessibility audits: paste a URL, we render the page in actual Chromium, press Tab to trace keyboard focus, compute color contrast from computed styles, and return a scored report with rule citations you can file as tickets.
Live: https://checker.lazynext.com/ API: https://accessibility-checker.dry-hall-6a50.workers.dev
curl -X POST https://accessibility-checker.dry-hall-6a50.workers.dev/scan \
-H 'content-type: application/json' \
-d '{"url": "https://yoursite.com", "license": "you@example.com", "email_report": true}'
# → {"score": 70, "score_model": "weighted-v1", "issues": [{"rule": "wcag-1.3.1", ...}],
# "rendered": true, "benchmark": {"pct": 61, "sites": 128},
# "report": ".../report/<id>"}The score is severity-weighted: confirmed WCAG level-A failures count in full, AA/AAA findings progressively less, warn-class heuristics at half, and repeat occurrences of the same rule at half marginal cost — a page full of minor nits outscores one with a few blocking failures.
Endpoints: POST /scan (html or url; {"url": ..., "site": true} crawls same-origin pages — 3 free / 10 Pro — and returns per-page scores; real-site scans also return benchmark — where the score ranks vs the corpus of sites scanned by this tool, shown once ≥10 sites are in), GET /checkout (trial → paid), POST /cancel (self-service cancellation by purchase email), POST /lead (email capture), GET /report/:id (shareable report — ?level=A|AA|AAA|BP, ?rule=, ?by=page views; CSV/JSON/PDF exports honor them), GET /badge/:id.svg (embeddable score badge for a report), GET /rules (the coverage manifest — 74 WCAG criteria + 1 best-practice check; name, level, WCAG version, and detection path for every check emitted; Accept: text/html returns a browsable catalog, JSON is the default), GET /openapi.json (OpenAPI 3.1 contract for the whole REST surface), POST /monitor / GET /monitor?license= / DELETE /monitor (Pro daily monitoring — platform rescans each registered URL and emails a Brevo alert when a page's score drops ≥ 10 points), GET /health.
Agent surfaces
tools/call; GET is 405, no SSE). Tools: scanurl, scanhtml, getreport, listrules. Add to an MCP client: {"mcpServers": {"a11y": {"url": "https://checker.lazynext.com/mcp"}}}
- MCP — POST /mcp, JSON-RPC 2.0 (initialize, tools/list,
handles message/send (send a text part containing a URL or HTML), tasks/send (alias), and tasks/get (the task id is the persisted report id). Scans return as completed tasks with the report artifact.
- A2A — agent card at GET /.well-known/agent.json; POST /a2a
data-target="#el"> mounts a Shadow-DOM scan box anywhere; optional data-license="buyer@x.com" for Pro.
- Widget — <script src="https://checker.lazynext.com/widget.js"
and persist the same 30-day reports.
- Scans through MCP/A2A share the /scan free quota (3 URL scans/day/IP)
SDKs + CLI
import { AccessibilityChecker } from './sdk/js/index.js';
const a11y = new AccessibilityChecker({ license: 'buyer@x.com' }); // license optional
const { score, issues, report } = await a11y.scan({ url: 'https://example.com' });
await a11y.site('https://example.com'); // same-origin crawl
await a11y.report(id); // stored report object (.json export)
await a11y.reportCsv(id); // CSV export
await a11y.rules(); // full coverage manifestc := checker.New("buyer@x.com") // license optional
res, err := c.Scan(checker.ScanOptions{URL: "https://example.com"})
rep, _ := c.Report(id) // stored report object (.json export)
rules, _ := c.Rules()from lazynext_a11y import AccessibilityChecker # sdk/python, stdlib only
c = AccessibilityChecker(license="buyer@x.com") # license optional
res = c.scan(url="https://example.com")Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Lazynext Accessibility Checker: common questions
- Is Lazynext Accessibility Checker MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Lazynext Accessibility Checker safety report
- How do I install Lazynext Accessibility Checker?
- It runs remotely at api.lazynext.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Lazynext Accessibility Checker need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Lazynext Accessibility Checker maintained?
- The last commit was 33 days ago (2026-10-02). The latest release is v1.0.0.
- Is Lazynext Accessibility Checker up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Lazynext Accessibility Checker?
- Servers from other publishers that do the same job: Autopilot Jobhunt MCP server, MCP ZAP Server MCP server and mcp-audit MCP server.
- How does Lazynext Accessibility Checker compare with other Security MCP servers?
- safety score 91/100 (higher than 90% of 915 Security servers); tools 4 (the typical Security server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Lazynext Accessibility Checker
Same job from other publishers: the closest match first, then the best rated.
- Autopilot JobhuntAgentic job hunt: scan careers pages, score against your resume, draft applications. Never applies.not reviewedGrowingA
MCP ZAP ServerSafe, self-hosted ZAP operator for guided AI security scans and reports.not reviewedGrowingB- mcp-auditScan, enumerate, and risk-score every MCP server configured on your machine.not reviewedGrowingA
- Security Txt Cra Lint13 rules that decide whether a vulnerability report ever reaches younot reviewedGrowingA
- PyMemoryEditorRead, write and scan process memory, Cheat Engine style, on Windows, Linux and macOS.not reviewedEstablishedA