AllyProof Accessibility
MCP server by AllyProof
Scan public web pages for WCAG 2.2 AA accessibility violations and get fix guidance for each finding.
Connect to AllyProof Accessibility
No sign-in needed. Connect with AllyProof Accessibility’s own URL:
Paste it into any client that supports remote MCP servers. Your client talks to AllyProof directly, not through mcp.tc.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/allyproof-accessibilityAbout
AllyProof scans a single web page for WCAG 2.2 AA accessibility issues using axe-core, HTML_CodeSniffer and APCA. It returns a score from 0 to 100, a severity breakdown, and up to 20 violations with WCAG criteria, descriptions and how to fix them.
The hosted endpoint uses streamable HTTP. The scan_url tool works on any public URL with no sign-in or API key. An API key sent in the x-api-key header unlocks list_sites, scan_site and list_violations for your own sites. Automated results need human review and do not establish conformance.
What you can do
- Scan any public URL for WCAG 2.2 AA violations
- Get a 0-100 accessibility score with severity breakdown
- See up to 20 violations with WCAG criteria and fixes
- List and scan your own sites with an API key
- List violations for monitored sites with an API key
Tools 1
scan_urlRead-onlyScan one public web page for WCAG 2.2 AA violations and return a score, severity counts and up to…
Read from the live server on 18 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
Scan https://example.com for accessibility issues.
Check this page for WCAG 2.2 AA violations and tell me how to fix them.
Run a fresh accessibility scan of my staging homepage URL.
Which severity levels showed up in the accessibility scan of my landing page?
Set up
Every client connects to allyproof.com. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http allyproof-accessibility https://allyproof.com/api/mcp- Start Claude Code and type
/mcp. allyproof-accessibility should show as connected.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it AllyProof Accessibility and paste this URL:
https://allyproof.com/api/mcp- Click Add. Its tools appear in the chat’s tools menu.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://allyproof.com/api/mcpand click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://allyproof.com/api/mcpas the server URL, then for authentication choose No authentication. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"allyproof-accessibility": {
"url": "https://allyproof.com/api/mcp"
}
}
}VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"allyproof-accessibility","type":"http","url":"https://allyproof.com/api/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"allyproof-accessibility": {
"type": "http",
"url": "https://allyproof.com/api/mcp"
}
}
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"allyproof-accessibility": {
"serverUrl": "https://allyproof.com/api/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add allyproof-accessibility --url https://allyproof.com/api/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.allyproof-accessibility]
url = "https://allyproof.com/api/mcp"Gemini CLI
gemini mcp add --transport http allyproof-accessibility https://allyproof.com/api/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"allyproof-accessibility": {
"type": "http",
"url": "https://allyproof.com/api/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://allyproof.com/api/mcp.
Embed
Show AllyProof Accessibility in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/allyproof-accessibility)<a href="https://mcp.tc/i/allyproof-accessibility"><img src="https://mcp.tc/i/allyproof-accessibility/badge.svg" alt="AllyProof Accessibility on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/allyproof-accessibility.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/allyproof-accessibility" title="AllyProof Accessibility on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/allyproof-accessibility.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the AllyProof Accessibility card to your site.
Add the mcp.tc card for AllyProof Accessibility, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/allyproof-accessibility.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="allyproof-accessibility"><a href="https://mcp.tc/i/allyproof-accessibility">AllyProof Accessibility on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/allyproof-accessibility)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 02:42 UTC.
FAQ
Can I paste mcp.tc/i/allyproof-accessibility into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://allyproof.com/api/mcp, so your client talks to AllyProof Accessibility directly. The quick link is for sharing: it opens this page, with setup steps for every client.
Does AllyProof Accessibility need an API key or a sign-in?
No. AllyProof Accessibility doesn’t ask for an account or key.
Is AllyProof Accessibility a remote or a local server?
Remote. AllyProof hosts it at https://allyproof.com/api/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can AllyProof Accessibility do?
It has 1 tool: scan_url. You can scan any public URL for WCAG 2.2 AA violations, get a 0-100 accessibility score with severity breakdown and see up to 20 violations with WCAG criteria and fixes.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to AllyProof Accessibility?
Yes. AllyProof Accessibility’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read AllyProof Accessibility’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with AllyProof. This page was built from AllyProof Accessibility’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.