Home / MCP registry index / io.github.snayyar00/webability
io.github.snayyar00/webability
io.github.snayyar00/webability in the official MCP registry.
Endpoint https://mcp.webability.io/mcp. Source: github.com/snayyar00/webability-mcp.
The registry describes it as: Free WCAG 2.2/ADA/508 accessibility MCP: scan, AI fixes, verify, vision audit, localhost tunnel
We read its 17 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
scan_page verify_fix diff_scan start_audit add_site list_sites get_install_snippet create_upgrade_link get_audit flow_scan detect_framework generate_ai_fix visual_audit scan_html get_rules check_color_contrast check_aria
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-snayyar00-webability)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.