# AllyProof Accessibility MCP server

> Scan public web pages for WCAG 2.2 AA accessibility violations and get fix guidance for each finding.

- Listing: https://mcp.tc/i/allyproof-accessibility
- Connect: use the server's own URL `https://allyproof.com/api/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: AllyProof
- Homepage: <https://allyproof.com/>

## About

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 it 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_url`: Scan one public web page for WCAG 2.2 AA violations and return a score, severity counts and up to… (read-only)

## 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?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http allyproof-accessibility https://allyproof.com/api/mcp
```

2. 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

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **AllyProof Accessibility** and paste this URL:

```url
https://allyproof.com/api/mcp
```

3. 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

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=AllyProof%20Accessibility&connectorUrl=https%3A%2F%2Fallyproof.com%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://allyproof.com/api/mcp` and click **Add**.

3. 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

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://allyproof.com/api/mcp` as the server URL, then for authentication choose **No authentication**.

4. 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](<https://cursor.com/install-mcp?name=allyproof-accessibility&config=eyJ1cmwiOiJodHRwczovL2FsbHlwcm9vZi5jb20vYXBpL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "allyproof-accessibility": {
      "url": "https://allyproof.com/api/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=allyproof-accessibility&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fallyproof.com%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"allyproof-accessibility","type":"http","url":"https://allyproof.com/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "allyproof-accessibility": {
      "type": "http",
      "url": "https://allyproof.com/api/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "allyproof-accessibility": {
      "serverUrl": "https://allyproof.com/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add allyproof-accessibility --url https://allyproof.com/api/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.allyproof-accessibility]
url = "https://allyproof.com/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http allyproof-accessibility https://allyproof.com/api/mcp
```

This 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.

```json
{
  "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`.

## Recent changes

- 2026-11-04 17:53 UTC: 1 tool changed. Source: automatic check. Changed: scan\_url.
- 2026-10-29 11:21 UTC: Tracking started: 1 tool read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/allyproof-accessibility#history (Atom feed: https://mcp.tc/i/allyproof-accessibility/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.0.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-29
- Updated: 2026-10-29

---
Source: https://mcp.tc/i/allyproof-accessibility (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
