# RatedWithAI accessibility checker (remote · ratedwithai.com)

Scan a live web page for WCAG 2.1/2.2 AA issues with axe-core: score, grade, failing rules.

- Trust score: 88/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ratedwithai.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/com-ratedwithai-accessibility-checker/api-mcp.md), [page](https://verifymcp.io/servers/com-ratedwithai-accessibility-checker/api-mcp)

## Channel facts

- Endpoint: `https://ratedwithai.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 423 tokens (~211/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RatedWithAI accessibility checker MCP server?

RatedWithAI accessibility checker is a hosted endpoint at https://ratedwithai.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-ratedwithai-accessibility-checker 'https://ratedwithai.com/api/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ratedwithai-accessibility-checker": {
      "type": "remote",
      "url": "https://ratedwithai.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-ratedwithai-accessibility-checker --url 'https://ratedwithai.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ratedwithai-accessibility-checker:
    url: "https://ratedwithai.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ratedwithai-accessibility-checker": {
      "Transport": "http",
      "Url": "https://ratedwithai.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ratedwithai-accessibility-checker -t streamable-http -u 'https://ratedwithai.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-ratedwithai-accessibility-checker": {
      "type": "http",
      "url": "https://ratedwithai.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 88, +1)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 83, +1)

- [security] Tool “explain_accessibility_issue” rewrote its description, which is the text the model reads

### 2026-10-22 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `scan_accessibility` (~142 tokens)

Scan a website for accessibility issues

Use this when the user wants a public website or web page checked for accessibility (WCAG 2.1/2.2 AA, ADA, EAA, Section 508): it loads the live page in a real browser, runs axe-core on it and up to two more same-site pages, and returns a 0-100 score, a letter grade and the failing rules with example elements. Takes 15-40 seconds. Do not use it for pages that need a login, for localhost or private-network addresses, or for pasted HTML.

Input parameters:

- `url` (string, required): Public website address, e.g. example.com or https://example.com/about

Output parameters:

- `affectedElementCount` (integer)
- `failingRuleCount` (integer)
- `grade` (string)
- `moreInfoUrl` (string): Informational page on scheduled re-scans and fix help for this kind of result.
- `needsReviewCount` (integer): Checks axe could not decide automatically; a human must confirm them.
- `pagesScanned` (integer)
- `rulesOmitted` (integer): Failing rules not listed because the response is capped.
- `scannedAt` (string)
- `score` (number): 0-100, weighted by violation severity.
- `url` (string): The URL that was scanned, after normalisation.
- `violations` (array)

### `explain_accessibility_issue` (~93 tokens)

Explain how to fix an accessibility rule

Use this when the user asks what an axe-core accessibility rule means or how to fix it — such as color-contrast, image-alt, label or link-name. Returns plain-English steps and a code example. Do not use it when the user wants a site checked; it explains a rule and does not scan pages.

Input parameters:

- `rule_id` (string, required): axe-core rule id, e.g. color-contrast

Output parameters:

- `codeExample` (string)
- `known` (boolean)
- `referenceUrl` (string)
- `ruleId` (string)
- `steps` (array)
- `summary` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ratedwithai-accessibility-checker/api-mcp#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 87
- 2026-11-02: 87
- 2026-11-01: 86
- 2026-10-31: 86
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 85
- 2026-10-27: 84
- 2026-10-26: 84
- 2026-10-25: 83
- 2026-10-24: 83
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 78
- 2026-10-12: 77
- 2026-10-10: 76

## Common questions

### What is the RatedWithAI accessibility checker MCP server?

RatedWithAI accessibility checker is an MCP server listed in the public MCP registry as com.ratedwithai/accessibility-checker. Scan a live web page for WCAG 2.1/2.2 AA issues with axe-core: score, grade, failing rules. This page covers its hosted endpoint (https://ratedwithai.com/api/mcp).

### Is the RatedWithAI accessibility checker MCP server safe to use?

RatedWithAI accessibility checker scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the RatedWithAI accessibility checker MCP server expose?

RatedWithAI accessibility checker exposes 2 tools: scan_accessibility, explain_accessibility_issue. Their descriptions and schemas cost roughly 235 tokens of context every time the server is loaded.

### Does the RatedWithAI accessibility checker MCP server require authentication?

No. We connected to RatedWithAI accessibility checker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RatedWithAI accessibility checker MCP server still maintained?

RatedWithAI accessibility checker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ratedwithai.com/api/mcp
- Website: https://ratedwithai.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-ratedwithai-accessibility-checker/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ratedwithai-accessibility-checker/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-ratedwithai-accessibility-checker/api-mcp