← Registry tracker

mcp.webyes.com

Automating your accessibility workflows where you already work

Primary Subcategory
Test Automation & QA
View in the Claude registry
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
Developer Tools

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Test Automation & QA

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Brand
WebYes
Access
Account required
First tracked
2026-09-22
Tool count
11
Geography
US

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 showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory
10 scoredVerified connectors by score · Community connectors A–Z
Primary Subcategory
1Atlassian MCP81/100
2YouTrack70/100
3Linear68/100
4Sentry18/100
5DevRev17/100
—AccessLintPending VerificationGet notified
—AutonomaPending VerificationGet notified
—BetterBugsPending VerificationGet notified
—Cypress CloudPending VerificationGet notified
—LimrunPending VerificationGet notified
—mablPending VerificationGet notified
—mcp.webyes.comPending VerificationGet notified
—MeticulousPending VerificationGet notified
—OctoPerf MCPPending VerificationGet notified
—QA WolfPending VerificationGet notified
—QA.techPending VerificationGet notified
—RamsPending VerificationGet notified
—SnapVisorPending VerificationGet notified
—StarkPending VerificationGet notified
—ThundersPending VerificationGet notified
Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
Tools

11 tools agents can invoke

mcp.webyes.com FAQ
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.

What are mcp.webyes.com alternatives on Claude?

As of 2026-09-28, mcp.webyes.com competes with Atlassian MCP, YouTrack, Linear, Sentry, DevRev, Natoma, Runway (runway.team), Fullstory, Subtext, Jam, AccessLint, Autonoma, BetterBugs, Cypress Cloud, Limrun, mabl, Meticulous, OctoPerf MCP, QA Wolf, QA.tech, Rams, SnapVisor, Stark, Thunders in Claude Test Automation & QA, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.