Skip to content

EaseWeb accessibility MCP server

dev.easeweb/easewebeaseweb.devstreamable-httpv1.0.0Scanned

Accessibility guides for coding agents: fixes with working code, test steps, contrast checks. EN/JA

5 tools: 3 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • 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 EaseWeb accessibility MCP server can do

The EaseWeb accessibility MCP server is published by easeweb.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: before_building, test_steps and check_palette), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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 9, 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.

5 tools

Changes things 3Claude Code: ask
  • before_buildingAccessibility requirements for an interactive component or screen that is about to be designed or built: menus, dialogs, carousels, tabs, forms, drag and drop, custom controls, car…No 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.
    Description, as the server wrote it
    Accessibility requirements for an interactive component or screen that is about to be designed or built: menus, dialogs, carousels, tabs, forms, drag and drop, custom controls, cards, tables, charts, animation, and the wireframes, mockups and prototypes for them. Takes the request in the user’s own words and returns the guides that apply with the requirements to build in from the start (keys, roles and names, focus, what is announced), working reference code, and the checks split into what an agent can confirm and what a person must. When the request itself breaks a rule (autoplay with no pause, a placeholder as the only label, a div as a button, hover-only menus, removed focus outlines, disabled zoom), it also returns a version that keeps what the user wanted and passes, and one sentence that explains the change.

    Annotations the server declares

    • title: Before building: requirements and reference code
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_paletteChecks the contrast of colours, a palette or design tokens for use in a design or in code.No 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.
    Description, as the server wrote it
    Checks the contrast of colours, a palette or design tokens for use in a design or in code. Takes colour pairs (foreground and background, with text size in px and weight when the foreground is text, or use: "non-text" for control borders, icons and focus rings) or a set of named tokens, in hex, rgb() or hsl(). Returns each pair’s contrast ratio, pass or fail against WCAG 1.4.3 (text) and 1.4.11 (non-text) at AA or AAA, the nearest passing shade of the same hue, and the guides that apply. It checks values, not rendered pages: text over images, real focus states and forced colors stay with the audit.

    Annotations the server declares

    • title: Check colour contrast for text and controls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • test_stepsThe test plan for something that has been built or fixed.No 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.
    Description, as the server wrote it
    The test plan for something that has been built or fixed. For a guide (by slug) or a component (by query) returns the pass criteria, the checks an agent can run itself, the checks only a person can do (which keys to press and what should happen, as a two-minute script), the guide’s limits, and a Playwright regression test skeleton. An agent or automation can’t establish the person’s checks.

    Annotations the server declares

    • title: How to test a fix: agent checks and the person’s script
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • find_fixSearches the Learn guides by words, component name, tag, ARIA attribute or WCAG number (1.4.3, SC 2.1.1, JIS 達成基準, EN 301 549 9.x).No findings

    Why it is in this group

    • The name "find_fix" says "find": a word for reading.
    Description, as the server wrote it
    Searches the Learn guides by words, component name, tag, ARIA attribute or WCAG number (1.4.3, SC 2.1.1, JIS 達成基準, EN 301 549 9.x). Returns for each matching topic: the problem, the fix in one line, how to test it, the guide link, and the criterion in WCAG terms, with EN 301 549 and Section 508 in English or JIS X 8341-3 in Japanese. Topics with no guide yet come back as "in progress". For a finding, a complaint, a failing check or a question that names a problem.

    Annotations the server declares

    • title: Find the fix for an accessibility problem
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_guideThe full guide as Markdown, the same guide as easeweb.dev/learn/<slug>.md: what happens, why it fails, who it affects, what automation misses, the Before and After code, how to ver…No findings

    Why it is in this group

    • The name "get_guide" says "get": a word for reading.
    Description, as the server wrote it
    The full guide as Markdown, the same guide as easeweb.dev/learn/<slug>.md: what happens, why it fails, who it affects, what automation misses, the Before and After code, how to verify, and the limits. Also returns the After code as plain text with its marks (recommended, not enough on its own, the rule of thumb behind it). Takes a guide slug, as listed in find_fix and before_building results.

    Annotations the server declares

    • title: Get one guide as Markdown
    • 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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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 18, 2026, 16:24 UTC, unchanged since Oct 27, 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
3
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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://easeweb.dev/mcp: tools/list returned 5 tools to an anonymous client, including before_building (write), test_steps (write), check_palette (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. Tools5 changed.~5 changedView diff

Install

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

claude mcp add --transport http easeweb https://easeweb.dev/mcp
claude mcp add --transport http easeweb https://easeweb.dev/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__easeweb__find_fix",
      "mcp__easeweb__get_guide"
    ],
    "ask": [
      "mcp__easeweb__before_building",
      "mcp__easeweb__test_steps",
      "mcp__easeweb__check_palette"
    ],
    "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 easeweb. Review it before you use it.

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/dev.easeweb/easeweb/verify?hash=2fca6b56582b149b4535bc702aefd9db4eae18da3261d83d8d2a64df14373b58" | jq -e '.changed == false'

Pinned hash 2fca6b56582b, from Nov 9, 2026, 13:17 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.easeweb/easeweb/changes.xml

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

Badge

Anlyon Radar badge for dev.easeweb/easeweb
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.easeweb/easeweb.svg)](https://radar.anlyon.com/servers/dev.easeweb/easeweb)

Source: MCP Registry. Synced Oct 26, 2026, 23:17 UTC.

EaseWeb accessibility MCP server: questions and answers

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

Is the EaseWeb accessibility MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 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 EaseWeb accessibility MCP server delete data?

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

Can the EaseWeb accessibility 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 EaseWeb accessibility MCP server have?

5 tools: 3 write, 2 read. before_building, test_steps, check_palette, find_fix and get_guide.

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

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

Does the EaseWeb accessibility MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the EaseWeb accessibility MCP server changed its tools?

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