mcp.webyes.com
Automating your accessibility workflows where you already work
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
The WebYes MCP Server is a read-only Model Context Protocol (MCP) server that gives AI assistants and other MCP-compatible applications access to website accessibility scan data from WebYes. It allows connected AI tools to retrieve and work with the results of accessibility scans performed in WebYes, including identified accessibility issues and relevant information about those findings. This makes it easier to explore scan results, understand accessibility problems, ask questions about identified issues, and use scan data as context when planning accessibility improvements. The server provides read-only access, meaning connected applications can retrieve and analyze WebYes scan data but cannot modify scan results, change WebYes settings, initiate changes to the website, or perform remediation on the user’s behalf. By making WebYes accessibility data accessible through MCP, teams can incorporate accessibility insights into AI-assisted workflows while keeping WebYes as the source of the underlying scan data.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-22
- Tool count
- 11
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
11 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.