# io.github.snayyar00/webability (remote · mcp.webability.io) Free WCAG 2.2/ADA/508 accessibility MCP: scan, AI fixes, verify, vision audit, localhost tunnel - Trust score: 80/100 (high trust) - Change this week: +5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-10-17 ## Components - remote · `mcp.webability.io`: 80/100 (this document), [markdown](https://verifymcp.io/servers/snayyar00-webability/mcp.md), [page](https://verifymcp.io/servers/snayyar00-webability/mcp) - npm · `@webability/mcp`: 91/100, [markdown](https://verifymcp.io/servers/snayyar00-webability/webability-mcp.md), [page](https://verifymcp.io/servers/snayyar00-webability/webability-mcp) ## Channel facts - Endpoint: `https://mcp.webability.io/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.9.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-10-17. - **Endpoint Security**: 83/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 73/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 10382 tokens (~576/item across 18 items; 17 tools + 1 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 43/100 - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. - Supports UI / widget rendering. ## Install ### How do I install the io.github.snayyar00/webability MCP server? io.github.snayyar00/webability is a hosted endpoint at https://mcp.webability.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http snayyar00-webability 'https://mcp.webability.io/mcp' ``` ### Cursor ```json { "mcpServers": { "snayyar00-webability": { "url": "https://mcp.webability.io/mcp" } } } ``` ### VS Code ```json { "servers": { "snayyar00-webability": { "type": "http", "url": "https://mcp.webability.io/mcp" } } } ``` ### Codex ```toml [mcp_servers.snayyar00-webability] url = "https://mcp.webability.io/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "snayyar00-webability": { "type": "remote", "url": "https://mcp.webability.io/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add snayyar00-webability --url 'https://mcp.webability.io/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: snayyar00-webability: url: "https://mcp.webability.io/mcp" ``` ### Netclaw ```json { "McpServers": { "snayyar00-webability": { "Transport": "http", "Url": "https://mcp.webability.io/mcp" } } } ``` ### Vellum ```bash assistant mcp add snayyar00-webability -t streamable-http -u 'https://mcp.webability.io/mcp' ``` ### Other ```json { "mcpServers": { "snayyar00-webability": { "type": "http", "url": "https://mcp.webability.io/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-10-17 (score 80, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “verify_fix” rewrote its description, which is the text the model reads ### 2026-10-16 (score 80, +3) - [security] The server rewrote its instructions, which are the text every model session reads - [functional] The server now declares the “resources” capability - [functional] First check of Schema quality: 100 - [functional] First check of Capabilities: pass - [functional] New resource “webability-result-card” ### 2026-10-15 (score 77, +1) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “verify_fix” rewrote its description, which is the text the model reads - [security] Tool “start_audit” rewrote its description, which is the text the model reads - [security] Tool “visual_audit” rewrote its description, which is the text the model reads ### 2026-10-14 (score 76, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “scan_page” rewrote its description, which is the text the model reads - [functional] Server version: 1.8.2 → 1.9.0 ### 2026-10-13 (score 76, 0) - [security] Tool “flow_scan” rewrote its description, which is the text the model reads - [functional] Server version: 1.8.1 → 1.8.2 - [cosmetic] “flow_scan” reworded the description of “autoNavigate” - [cosmetic] “flow_scan” made “autoNavigate” optional ### 2026-10-12 (score 76, +1) - [functional] Server version: 1.8.0 → 1.8.1 ### 2026-10-10 (score 75, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-09 (score 74, +1) No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (17) ### `scan_page` (~840 tokens) Scan a page for accessibility issues Scan a web page for WCAG accessibility issues. Works on any URL — deployed sites, localhost, staging. Returns `issues` (violations the scanner stands behind; findings the engines cannot decide are settled by the AI judge — a violation with a fix, or a pass recorded in `judged[]` with its reason — and anything unsettled is dropped, never listed for review) and a `summary`. On React ≤18 / Vue dev builds each issue carries `source` ({file, line, column, component}) read from the live component tree. Every issue carries a structured `fix.op` (add-attribute | set-attribute | remove-attribute | add-element | remove-element | add-text-content | suggest) with `fix.attribute` / `fix.value` when known, and a `fixability` tier (mechanical = apply as given; contextual = op known, value needs judgment; visual = needs rendered output, propose only). NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `format` (string): "compact" prints one line per element with rule metadata once. "json" returns every field (html, fix values, source). Default: JSON when it fits inline (under ~24k chars), otherwise compact plus a JS… - `level` (string): Highest WCAG conformance level to report. Default "AA" — Level AAA criteria are not reported. Pass "AAA" to include them (naming one AAA criterion in `wcag`, e.g. "3.2.5", also includes it). - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `minImpact` (string): Only findings at this severity or above (critical > serious > moderate > minor) - `rootSelector` (string): CSS selector to limit scan scope (optional) - `rules` (array): Only these rule ids (WebAbility type such as "missing_alt" or axe rule id such as "image-alt"). See get_rules. - `sourceRoot` (string): Local project root (local installs only). Issues without a framework `source` pointer get `sourceCandidates[]` — files whose contents match the selector's id/class/attribute tokens. - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string, required): URL to scan (e.g. https://webability.io or http://localhost:3000) - `viewport` (string): Viewport size (default: desktop) - `wcag` (array): Only these WCAG criteria. A prefix selects the whole guideline ("1.4") or principle ("2"). ### `verify_fix` (~794 tokens) Verify an accessibility fix Re-scan a specific element after applying an accessibility fix and confirm the violation is gone. After you edit the code and serve it (deployed, staging, or http://localhost:3000), call this with the URL and the selector you fixed to get a machine-checked verified: true|false (DOM engines only — visual_audit findings are out of scope). Pass the WCAG criterion (e.g. "1.1.1") or axe rule id (e.g. "color-contrast") to check just that criterion; omit it to require the element be clean of ALL violations. A blocked page (bot-challenge / HTTP error) is reported as unverified, never a pass — verification fails closed. verified: true is only returned when the selector matched at least one element AND the criterion is one the DOM engines check; if the selector matches no element the result is verified: false with reason "not-found" ("selector matched no elements"), a criterion outside the coverage set returns reason "not-verifiable" ("not checked by any WebAbility tool"); a finding in scope that only the AI judge can settle, when the judge did not run or gave no verdict, also returns "not-verifiable", and shadow-DOM (>>>) / iframe selectors return "unsupported-selector" — pass the element's current selector, or re-run scan_page if your fix removed the element. Pair with scan_page → generate_ai_fix → verify_fix for a full find-fix-verify cycle. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `selector` (string, required): CSS selector of the element you fixed — use the `selector` from the original scan_page issue - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string, required): URL now serving the fix (deployed, staging, or http://localhost:3000). Also accepted as `page` or `pageUrl`. - `viewport` (string): Viewport size (default: desktop). Use the same viewport the issue was found at. - `wcag` (string): Optional: WCAG criterion (e.g. "1.1.1", "1.4.3") or axe rule id (e.g. "color-contrast") to verify specifically. Omit to require the element be free of ALL violations. ### `diff_scan` (~864 tokens) Compare two accessibility scans Compare two scans of the same page and report what changed: `fixed[]` (in the baseline, gone now), `new[]` (regressions — not in the baseline, present now), `remaining[]` (still there). Page-level complement to verify_fix (one element). Baseline is a scan_history id (`baselineId`, local installs) or a live scan of `baselineUrl`; current is `url` (scanned live now) or another history id (`currentId`). Findings are matched by issue id (rule + element), so a changed class/id on a fixed element reads as fixed AND new — check `new[]` before calling it a regression. Typical loop: scan_page → edit → diff_scan(baselineId=, url=) → confirm new[] is empty. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `baselineId` (string): scan_history id of the BASELINE scan (local installs only) - `baselineUrl` (string): Scan this URL live as the baseline (e.g. production) — use when there is no stored baseline - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `currentId` (string): scan_history id to use as the CURRENT side instead of scanning `url` - `format` (string): "compact" prints one line per element with rule metadata once. "json" returns every field (html, fix values, source). Default: JSON when it fits inline (under ~24k chars), otherwise compact plus a JS… - `level` (string): Highest WCAG conformance level to report. Default "AA" — Level AAA criteria are not reported. Pass "AAA" to include them (naming one AAA criterion in `wcag`, e.g. "3.2.5", also includes it). - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `minImpact` (string): Only findings at this severity or above (critical > serious > moderate > minor) - `rootSelector` (string): CSS selector to limit live scans to (optional) - `rules` (array): Only these rule ids (WebAbility type such as "missing_alt" or axe rule id such as "image-alt"). See get_rules. - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string): URL to scan now as the CURRENT side (deployed, staging, or http://localhost:3000). Omit when passing currentId. - `viewport` (string): Viewport for live scans (default: desktop). Use the same viewport the baseline used. - `wcag` (array): Only these WCAG criteria. A prefix selects the whole guideline ("1.4") or principle ("2"). ### `start_audit` (~558 tokens) Start a full accessibility audit Kick off a FULL accessibility audit deliverable for a URL — a persistent, timestamped artifact, not an inline scan. Runs the server-side pipeline (axe + advanced checks + mobile viewports + annotated screenshots + optional agent spot-check) and produces a downloadable report and a formatted Excel workbook (Cover / Status / Barriers / ADA context sheets) stored durably. Returns immediately with an audit `id`; poll `get_audit` for progress and, when complete, download URLs. Use this when someone needs a durable artifact to attach as evidence of testing effort for a compliance officer or legal response — for iterating on code, use scan_page + verify_fix instead. Needs a free WebAbility account (sign in by connecting https://mcp.webability.io/mcp/auth, or run `webability login`). Set includeAgent:true to add the slower agentic manual-audit pass. To audit a local dev server, open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` with the printed secret as `tunnel_secret`; keep the tunnel open until get_audit reports complete (about 5 minutes) — the pipeline loads the page several times. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `includeAgent` (boolean): Also run the agentic manual-audit pass (keyboard/focus/modal exploration). Slower. Default false. - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string, required): URL to audit (a public/staging URL the server can reach, or a webability-tunnel URL — not localhost) ### `add_site` (~327 tokens) Add a site to the account Add a website to the signed-in WebAbility account. The site gets the full widget for its first 30 days and a first scan. Returns the site id and plan tier. Next: put the get_install_snippet tag on the site, and use create_upgrade_link to get a payment link for the WebAbility Pro plan. Needs a free WebAbility account (an AI agent can sign itself up with "Sign in with AgentID"). Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `url` (string, required): The site to add, for example https://shop.example.com. One domain per site. ### `list_sites` (~262 tokens) List the account sites and plans List the sites on the signed-in WebAbility account with each site id, plan tier and the date the current plan ends. Use it to check that a payment activated WebAbility Pro on a site. Needs a free WebAbility account. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… ### `get_install_snippet` (~276 tokens) Get the widget install tag Get the one-line script tag that installs the WebAbility accessibility widget. Put it in the or before of every page of a site added with add_site. The widget finds the site by its domain, so the same tag works on every site. No account needed. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… ### `create_upgrade_link` (~326 tokens) Get a WebAbility Pro payment link Get a Stripe Checkout link that puts one site on the WebAbility Pro plan (the widget subscription). Give the link to the human who pays (your owner). When they pay, the plan activates on that site automatically; check with list_sites. You never handle card details. The site must be on the account (add_site first). Needs a free WebAbility account. Input parameters: - `billing_interval` (string): Billing period. Default monthly. - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `domain` (string, required): The site to upgrade, as added with add_site (for example shop.example.com) - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… ### `get_audit` (~315 tokens) Get audit status and report Check an audit started with start_audit: returns overall status, per-step progress (scan → viewports → screenshots → agent → excel → publish), and — once complete — a severity summary plus short-lived download URLs for the report (JSON) and the Excel workbook. Poll every ~15s while status is pending/running. Only the account that started an audit can read it. Free with a WebAbility account. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `id` (number, required): The audit id returned by start_audit - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… ### `flow_scan` (~792 tokens) Scan a multi-page user flow Scan a multi-page user journey. Walks startUrl plus the `autoNavigate` URLs sequentially (deterministic — one page fully rendered and scanned before the next), then returns ONE consolidated report with issues deduplicated across pages, each carrying the same fix payload as scan_page. Every requested URL gets an explicit outcome in `pages[]` (scanned / nav_failed / scan_failed / redirected_duplicate / duplicate_request / skipped_cap / blocked — bot-challenge, not a clean page) — a page is never silently dropped. Better than per-page scans for journeys (login → checkout etc). Without `autoNavigate` it scans only startUrl, exactly like scan_page. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `autoNavigate` (array): The URLs to walk after startUrl, in order (the MCP server is headless and cannot discover a journey interactively). Omit or pass [] to scan only startUrl as a single page. - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `format` (string): "compact" prints one line per element with rule metadata once. "json" returns every field (html, fix values, source). Default: JSON when it fits inline (under ~24k chars), otherwise compact plus a JS… - `level` (string): Highest WCAG conformance level to report. Default "AA" — Level AAA criteria are not reported. Pass "AAA" to include them (naming one AAA criterion in `wcag`, e.g. "3.2.5", also includes it). - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `maxPages` (number): Max pages to scan (default 10) - `minImpact` (string): Only findings at this severity or above (critical > serious > moderate > minor) - `rules` (array): Only these rule ids (WebAbility type such as "missing_alt" or axe rule id such as "image-alt"). See get_rules. - `sourceRoot` (string): Local project root (local installs only) for `sourceCandidates[]` on issues without a framework `source` pointer. - `startUrl` (string, required): Starting URL of the journey - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `wcag` (array): Only these WCAG criteria. A prefix selects the whole guideline ("1.4") or principle ("2"). ### `detect_framework` (~465 tokens) Detect the site framework Detect a page's stack as two separate fields: `framework` — the application framework, CMS or site builder (e.g. nextjs, nuxt, sveltekit, vitepress, astro, gatsby, wordpress, shopify, mediawiki, vue, react; "unknown" when no signal) — and `cssToolkit` (tailwind, bootstrap, mui, plain-css). Lists the evidence it used and the value to pass as generate_ai_fix `framework`. scan_page reports the same two fields from the same detection. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string, required): URL to inspect ### `generate_ai_fix` (~436 tokens) Suggest a framework-aware fix Generate framework-aware fix alternatives for a specific accessibility issue. For color contrast issues, returns 3 alternatives (minimal, brand-aligned, high contrast); brand palette is auto-extracted from the live URL using our scanner if `brandColors` is omitted. For label/ARIA issues, returns 1-2 alternatives. Each alternative includes ready-to-paste code for the detected framework. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `brandColors` (array): Brand palette for brand-aligned suggestions. If omitted on a contrast issue with a `url`, auto-extracted via the scanner. - `context` (string): Parent element outerHTML for context (~400 chars) - `framework` (string, required): CSS framework — use detect_framework first - `html` (string, required): The element's outerHTML — send at most ~600 chars - `issue` (object|string, required): Issue object from scan_page (with selector, wcag, impact, message, fix.currentValue), or a plain-text issue description - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string): Page URL — also used to auto-extract brand palette for contrast issues if `brandColors` is not provided. ### `visual_audit` (~546 tokens) Visual accessibility audit Pixel-level accessibility audit using Claude vision. Catches issues that DOM scanners miss: icon contrast (1.4.11), focus visibility (2.4.7), "looks like a button but isn't" (4.1.2), text rendered as images (1.4.5), visual hierarchy mismatches. Takes a URL, opens it in a headless browser, screenshots, and runs vision-based detection. Complements scan_page — run both for full coverage. Sign in with a free WebAbility account for vision and full audits (sign in by connecting https://mcp.webability.io/mcp/auth, or run `webability login`). Fair-use rate limits apply. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `brandColors` (array): Brand hex colors for context-aware filtering - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `fullPage` (boolean): Capture full scrolled page instead of just viewport (default: false) - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string, required): URL to audit visually - `viewport` (string): Viewport size (default: desktop) ### `scan_html` (~687 tokens) Scan an HTML snippet Scan a raw HTML snippet or component markup without serving it — IN-PROCESS by default (jsdom + WebAbility detectors + axe-core): milliseconds, no browser, no network, so it fits inside a tight edit loop. Fragments are auto-wrapped into a document. Returns scan_page's shape (issues / summary) with `fix.op` + `fixability` on every finding. jsdom has no layout, so visual-tier rules (contrast, target size, focus ring) are NOT evaluated — the dropped count is reported as `skippedVisual`; pass `engine: "browser"` to run the axe-core headless-browser path for those (slower, axe rules only, returns axe `violations`). Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `engine` (string): "in-process" (default): jsdom, ms, structural rules. "browser": headless Chromium + axe-core, includes contrast. - `format` (string): "compact" prints one line per element with rule metadata once. "json" returns every field (html, fix values, source). Default: JSON when it fits inline (under ~24k chars), otherwise compact plus a JS… - `height` (number): Viewport height (browser engine only, default 800) - `html` (string, required): HTML content to test — a full document or a fragment - `level` (string): Highest WCAG conformance level to report. Default "AA" — Level AAA criteria are not reported. Pass "AAA" to include them (naming one AAA criterion in `wcag`, e.g. "3.2.5", also includes it). - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `minImpact` (string): Only findings at this severity or above (critical > serious > moderate > minor) - `rules` (array): Only these rule ids (WebAbility type such as "missing_alt" or axe rule id such as "image-alt"). See get_rules. - `tags` (array): WCAG tags to check (default ["wcag2a","wcag2aa","wcag21aa","wcag22aa"]) - `wcag` (array): Only these WCAG criteria. A prefix selects the whole guideline ("1.4") or principle ("2"). - `width` (number): Viewport width (browser engine only, default 1280) ### `get_rules` (~453 tokens) List accessibility rules List accessibility rules from both engines — axe-core (104) and the WebAbility detectors (90+) — with optional filters. Every rule carries `fixability` (mechanical | contextual | visual) and a `fix` op template, so you can pick the rules worth auto-fixing before scanning. Returns ruleId, engine, description, help, helpUrl, tags/wcag, fixability, fix. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `engine` (string): Which engine's rules to list (default all) - `fixability` (string): Only rules of this fixability tier - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `rule` (string): Only rules whose id contains these whole words (e.g. "link" → link-name, skip-link, not blink; "color-contrast"; case and -/_ insensitive). Also accepted: ruleId, id, query. - `tags` (array): axe tag filter (e.g. ["wcag2aa"], ["best-practice"], ["cat.aria"]; a category also works without "cat."). WebAbility rules match on their WCAG criterion tag (e.g. "wcag143"). An unknown tag or catego… ### `check_color_contrast` (~745 tokens) Check color contrast Check text contrast against the WCAG AA threshold (4.5:1, or 3:1 for large text); the AAA verdict is shown only when you pass level: "AAA". Either pass a `foreground` / `background` color pair, or pass `url` + `selector` to read the element's own text color, background (composited from the nearest painted ancestors), font size and weight from the live page; explicit colors win over the page. A gradient or image background is reported as an error, never a guessed ratio. When it fails, suggests BRAND-aligned replacements — extracts the actual brand palette from the `url` page using our scanner (CSS vars + most-used colors), or use a provided `brandColors` array. No `url` and no `brandColors` = ratio + pass/fail only. NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `background` (string): Background color (hex or rgb). Optional with url + selector. - `brandColors` (array): Pre-supplied brand palette. Skips URL extraction if provided. - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `fontSize` (number): Font size in px (default 16, or the element's computed size with url + selector) - `foreground` (string): Foreground color (hex or rgb). Optional with url + selector. - `isBold` (boolean): Whether text is bold (default false, or the element's computed weight with url + selector) - `level` (string): Conformance level to judge. Default "AA". "AAA" adds the enhanced-contrast (1.4.6) verdict and AAA palette suggestions. - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `selector` (string): CSS selector of the text element on `url` (e.g. the `selector` from a scan_page issue) - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string): Live page: with `selector`, the colors are read from that element; on a failing pair, the brand palette is extracted from it (uses our scanner — CSS vars + dominant colors). ### `check_aria` (~573 tokens) Validate ARIA in HTML or on a page Validate ARIA attribute + accessible name/role/value usage — in an HTML snippet (`html`) or on a live page (`url`), optionally limited to one element and its descendants (`selector`). Runs axe-core `cat.aria` and `cat.name-role-value` rules (aria-* attribute correctness, role validity, required parents/children, aria-hidden-focus, accessible names). Returns `violations`. A selector that matches nothing, or a page that answers an HTTP error, is an error — never "no violations". Nodes cap at 5 per rule by default — every rule reports nodesTotal + truncated; raise nodeLimit (max 50). NOTE: on this HOSTED server, localhost and private addresses are refused — it runs in our cloud and cannot reach your machine. Two ways to scan a local dev server: run the MCP locally (`npx -y @webability/mcp`, simplest — nothing leaves the machine), or open a tunnel (`webability-tunnel --port 3000`) and pass its URL as `url` together with the printed secret as `tunnel_secret`. Input parameters: - `context` (string): Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include,… - `html` (string): HTML to test for ARIA correctness (pass this or `url`) - `llm_model` (string): The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model… - `nodeLimit` (number): Max nodes returned per rule (default 5, max 50) - `selector` (string): Only report findings on this element and its descendants (e.g. the `selector` from a scan_page issue). ARIA references outside it still resolve. - `tunnel_secret` (string): Secret printed by `webability-tunnel`. Required when `url` is a tunnel URL; the URL alone will be refused by the relay. Ignored otherwise. - `url` (string): Live page to check (pass this or `html`) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/snayyar00-webability/mcp#diagnostics ## Score history - 2026-10-17: 80 - 2026-10-16: 80 - 2026-10-15: 77 - 2026-10-14: 76 - 2026-10-13: 76 - 2026-10-12: 76 - 2026-10-10: 75 - 2026-10-09: 74 - 2026-10-07: 73 - 2026-10-04: 72 ## Common questions ### What is the io.github.snayyar00/webability MCP server? io.github.snayyar00/webability is an MCP server listed in the public MCP registry as io.github.snayyar00/webability. Free WCAG 2.2/ADA/508 accessibility MCP: scan, AI fixes, verify, vision audit, localhost tunnel. This page covers its hosted endpoint (https://mcp.webability.io/mcp). ### Is the io.github.snayyar00/webability MCP server safe to use? io.github.snayyar00/webability scores 80 out of 100 on VerifyMCP. 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 io.github.snayyar00/webability MCP server expose? io.github.snayyar00/webability exposes 17 tools: scan_page, verify_fix, diff_scan, start_audit, add_site, and 12 more. Their descriptions and schemas cost roughly 9,259 tokens of context every time the server is loaded. ### Does the io.github.snayyar00/webability MCP server require authentication? No. We connected to io.github.snayyar00/webability without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the io.github.snayyar00/webability MCP server still maintained? io.github.snayyar00/webability is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://mcp.webability.io/mcp - Repository: https://github.com/snayyar00/webability-mcp - Website: https://webability.io/ - Changelog RSS feed: https://verifymcp.io/servers/snayyar00-webability/mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/snayyar00-webability/mcp.json - HTML version of this page: https://verifymcp.io/servers/snayyar00-webability/mcp