WCAG.com Accessibility MCP. Audit web compliance and retrieve detailed WCAG metadata.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
WCAG.com Accessibility Server audits web compliance by checking URLs against WCAG 2.1 standards. Your AI agent retrieves high-resolution reports, identifies specific accessibility issues (like color contrast or text scaling), and provides detailed remediation metadata for any site.
It helps you prove digital compliance without running manual checks.
What your AI agents can do
Audit url accessibility
Runs a full WCAG audit on an input URL and reports compliance markers.
Check api status
Verifies if the entire WCAG.com service is currently operational.
Get wcag guideline details
Pulls detailed metadata and specific recommendations for a named WCAG guideline.
The server runs a WCAG accessibility audit against a given URL, returning structured compliance reports.
It verifies the operational status of the entire WCAG.com API to ensure your research workflow stays active.
The server pulls detailed metadata and remediation recommendations for any specific WCAG guideline identifier.
It generates a full catalog of every accessibility rule currently used by the auditing engine.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
WCAG.com Accessibility MCP Server: 4 Tools for Web Compliance
These tools let you run deep audits, check API health, look up specific WCAG rules, or list all available accessibility standards.
019d849baudit url accessibility
Runs a full WCAG audit on an input URL and reports compliance markers.
019d849bcheck api status
Verifies if the entire WCAG.com service is currently operational.
019d849bget wcag guideline details
Pulls detailed metadata and specific recommendations for a named WCAG guideline.
019d849blist accessibility rules
Lists every accessibility rule used by the auditing engine, giving you a full catalog of standards.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with WCAG.com Accessibility, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You need proof that your site passes WCAG 2.1 standards, and this server gives you the data without the guesswork. Your AI agent handles all the heavy lifting—you just point it at what you gotta check.
When you run an audit on a specific page, the audit_url_accessibility tool runs a full WCAG compliance check against any URL you give it, returning structured reports showing exactly where your site stands. It doesn't just tell you 'error'; it points out markers like color contrast issues or problems with text scaling and gives detailed remediation metadata so you know how to fix it immediately.
You get high-resolution reports that prove digital compliance without running through manual validators.
If you gotta dig into the standards themselves, two tools help. The list_accessibility_rules tool generates a full catalog of every single accessibility rule the auditing engine uses; this lets you see all the markers it's looking for across your whole site. For deeper knowledge on a specific requirement, you can use get_wcag_guideline_details.
This tool pulls detailed metadata and specific recommendations whenever you feed it a named WCAG guideline identifier.
When you need to verify that our research workflow is active, the system checks in with the check_api_status tool. Running this confirms whether the entire WCAG.com service is up and running, keeping your audit process moving when you're on a deadline.
This server lets your agent perform four core functions: auditing a specific web page by sending it through audit_url_accessibility; checking service uptime using check_api_status to make sure nothing breaks; looking up guideline details via get_wcag_guideline_details for deep technical specs; and finally, listing all compliance rules with list_accessibility_rules so you've got a complete view of the standards.
How WCAG.com Accessibility MCP Works
- 1 Subscribe to this server and provide your WCAG.com API Key.
- 2 Direct your AI client (Claude, Cursor, etc.) to perform a specific task—like 'Audit example.com' or 'What are the rules for 1.3.1?'.
- 3 The agent calls the appropriate tool, gets the structured report back, and presents the findings in natural language.
The bottom line is you use your AI client to talk to the WCAG data directly, bypassing manual web checks entirely.
Who Is WCAG.com Accessibility MCP For?
Compliance Officers who need to prove adherence to standards; QA Engineers who hate manually cross-referencing guidelines; Web Developers needing verifiable accessibility metadata. If you spend time checking if your site meets the WCAG standard, this is for you.
Performs rapid audits of client websites and identifies specific compliance markers using natural language queries.
Verifies WCAG standards across multiple pages by running bulk audits and checking issue patterns without manual searching.
Monitors site accessibility, retrieving official metadata directly into the development workflow to fix issues fast.
What Changes When You Connect
- Guaranteed Compliance Data. You get official, verifiable data straight from the source. Instead of relying on generalized checks, you use
audit_url_accessibilityfor real-world WCAG 2.1 reporting. - Deep Guideline Lookup. Need to know exactly what 'Success Criterion 1.3.1' requires? Use
get_wcag_guideline_details. It pulls the technical rules and implementation recommendations you need, period. - Full Rule Cataloging. Don't guess what standards apply. Run
list_accessibility_rulesto get a comprehensive catalog of every rule used by the WCAG engine—it’s your master checklist. - Immediate API Health Check. Before starting any audit, use
check_api_status. This confirms the entire service is up and running, so you don't waste time on broken connections. - Natural Language Auditing. Your agent handles the complexity. You simply ask: 'What are the color contrast issues on this page?' and it runs the audit for you.
Real-World Use Cases
Client Site Audit
A consultant needs to quickly assess a client's homepage. They run audit_url_accessibility against the URL, find 12 issues (color contrast, text scaling), and then use get_wcag_guideline_details to pull specific remediation steps for those findings into their report.
Pre-Development QA
A developer is building a new component. They ask the agent to run list_accessibility_rules. This lets them see every required standard before writing code, ensuring they hit all compliance markers upfront.
Debugging an Issue
The QA team finds a weird error and needs context. They use get_wcag_guideline_details for the specific guideline ID to understand the failure criteria, rather than just receiving a vague error message.
Verifying Tool Reliability
The Ops team wants to ensure their entire workflow is stable. They first run check_api_status before launching any audits. This simple check confirms the API is operational, preventing failed reports and delays.
The Tradeoffs
Using general AI prompts
Asking your agent simply to 'Check if my website is accessible.' The agent can only give a high-level summary without actionable data.
→
Always force the tool call. For instance, run audit_url_accessibility and then follow up with get_wcag_guideline_details on any specific failure point found in the audit.
Ignoring API status
Starting a complex compliance report only to have it fail halfway through because the external service is down. Wasted time and inaccurate reports.
→
Always check first. Run check_api_status before you start any major audit or data retrieval job.
Treating rules as a black box
Finding an error code but having no idea what standard it violates or how to fix it beyond a generic suggestion. The remediation is useless.
→
Use list_accessibility_rules to see the full context of standards, then use get_wcag_guideline_details for targeted fixes and specific technical requirements.
When It Fits, When It Doesn't
You should use this server if your primary need is verifiable, detailed compliance data that maps directly to WCAG 2.1 guidelines. It's ideal when you need the 'why' behind an accessibility error—not just that it exists.
Don't use this if you simply want a basic green/red light status or general user feedback (e.g., 'Does the site look good?'). For those, general UX tools will suffice. This server is for technical validation only.
If you need to build out an entire system of checks and monitoring, remember that running list_accessibility_rules provides the full scope, while pairing audit_url_accessibility with get_wcag_guideline_details gives you the actionable report needed by QA teams. If your issue is simply 'is it working right now?', run check_api_status. Never assume compliance; always verify.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by WCAG.com. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 4 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Checking for accessibility issues usually means opening 5 different tabs and running multiple validators.
Today, checking a site's compliance is manual hell. You run one validator for color contrast, another for ARIA roles, then you have to open the WCAG website separately just to figure out what 'Level AA' actually means in practice. You spend hours clicking between tools and tabs, cross-referencing error codes with dense documentation.
With this MCP server, your agent handles it all. You simply ask: 'Audit this page for color contrast issues.' It runs the check, finds the exact failure, and then immediately pulls up the official WCAG guidelines via `get_wcag_guideline_details`, giving you the fix—all in one chat response.
WCAG.com Accessibility MCP Server: Get precise reports with audit_url_accessibility.
Manual auditing forces you to treat every component as a separate test case, making it impossible to get a unified view of the site's compliance status across all defined standards. You lose context and spend more time on reporting than fixing.
Now, running `audit_url_accessibility` gives you a single, high-resolution report that covers multiple issues—from color contrast to text scaling—all while maintaining clear views of WCAG adherence. It's a complete audit cycle in one go.
Common Questions About WCAG.com Accessibility MCP
How do I check general accessibility compliance using the audit_url_accessibility tool? +
You run audit_url_accessibility and provide the URL. The server performs a WCAG 2.1 audit, returning structured reports that identify specific issues like color contrast failure or incorrect text scaling.
What is the difference between using list_accessibility_rules and get_wcag_guideline_details? +
list_accessibility_rules provides a full catalog of all standards used by the engine. get_wcag_guideline_details lets you focus in on one specific guideline (e.g., 1.1.1) to get its unique metadata and recommendations.
Can I check if the WCAG service is working before running an audit? +
Yes, that's what check_api_status does. You run this tool first; it verifies the API status, ensuring your subsequent audits don't fail due to external issues.
Does WCAG.com Accessibility MCP support all types of compliance? +
It focuses on web accessibility and digital compliance based on the authoritative WCAG standards (like 2.1). It isn’t a general website checker; it's a technical audit tool.
How do I authenticate or connect my API key when using audit_url_accessibility? +
You must provide a valid WCAG.com API Key during initial setup. This key authorizes your AI client to run any of the tools against external services, so make sure it's active before you start.
What happens if I run too many audits using audit_url_accessibility in a short time? +
Running this tool repeatedly may hit usage limits set by WCAG.com. If the process fails, check the API status first, wait for the specified cooldown period, or consider increasing your quota.
Does get_wcag_guideline_details provide implementation code or just guidelines? +
It provides structured remediation metadata and success criteria, not live coding examples. The output tells you exactly what technical requirement needs to be met for compliance.
Can list_accessibility_rules show rules from standards other than WCAG 2.1? +
No, the tool lists rules defined solely by the core WCAG auditing engine. It focuses on current WCAG standards; you can't pull in external rule sets this way.
How do I find my WCAG.com API Key? +
Log in to your WCAG.com account, navigate to the 'API Keys' section in your dashboard, and generate a new token. Copy and paste it below.
What compliance levels are supported? +
The API audits against WCAG 2.1 levels A, AA, and AAA, identifying issues for each category.
Does it provide remediation tips? +
Yes. The get_wcag_guideline_details tool retrieves specific implementation recommendations to help fix accessibility issues identified during audits.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Uptime.com
Monitor website and API uptime from 30+ global locations with instant alerts when downtime hits any of your services.
Dev.to (Forem)
Manage Dev.to and Forem articles — list posts, create content, and inspect user profiles directly from any AI agent.
Deterministic Base Converter
Equip your AI with infinite-precision mathematical conversion between any numerical bases (2 through 36), including Binary, Hexadecimal, and Octal.
You might also like
Adjust
Mobile measurement and attribution — track app installs, events, and performance via AI.
RocketLaunch.Live
Track rocket launches worldwide — search upcoming launches, vehicles, companies, locations and missions.
ArcXP
Automate newsroom publishing via ArcXP — manage, search, and update articles, photos, and videos directly from any AI agent.