Skip to content

RatedWithAI accessibility checker MCP server

com.ratedwithai/accessibility-checkerratedwithai.comstreamable-httpv1.0.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RatedWithAI accessibility checker MCP server can do

The RatedWithAI accessibility checker MCP server is published by ratedwithai.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: scan_accessibility), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (scan_accessibility); 1 tool can send data out of your system (scan_accessibility).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • scan_accessibilityUse 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-cor…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Scan a website for accessibility issues
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • explain_accessibility_issueUse 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.No findings

    Why it is in this group

    • The name "explain_accessibility_issue" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain how to fix an accessibility rule
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ratedwithai.com/api/mcp: tools/list returned 2 tools to an anonymous client, including scan_accessibility (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__accessibility-checker__explain_accessibility_issue"
    ],
    "ask": [
      "mcp__accessibility-checker__scan_accessibility"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as accessibility-checker. Review it before you use it.

Capability tags behind 1 rule
  • mcp__accessibility-checker__scan_accessibility untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.ratedwithai/accessibility-checker/verify?hash=f7c84c48d751465afc8d62006784d50b24839f0b86a1ea12de908ecfa221759f" | jq -e '.changed == false'

Pinned hash f7c84c48d751, from Nov 14, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.ratedwithai/accessibility-checker/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.ratedwithai/accessibility-checker
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ratedwithai/accessibility-checker.svg)](https://radar.anlyon.com/servers/com.ratedwithai/accessibility-checker)

Source: MCP Registry. Synced Oct 21, 2026, 18:01 UTC.

RatedWithAI accessibility checker MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RatedWithAI accessibility checker MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RatedWithAI accessibility checker MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RatedWithAI accessibility checker MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RatedWithAI accessibility checker MCP server have?

2 tools: 1 write, 1 read. scan_accessibility and explain_accessibility_issue.

Does the RatedWithAI accessibility checker MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RatedWithAI accessibility checker MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_accessibility.

Has the RatedWithAI accessibility checker MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 1, 2026. Every change is on this page and in its Atom feed.