EaseWeb accessibility
REMOTE · EASEWEB.DEV
Accessibility guides for coding agents: fixes with working code, test steps, contrast checks. EN/JA
Available components
Last scanned (16 hours ago)
Scores higher than 78% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 38141 tokens (~94/item across 405 items; 5 tools + 400 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
- New resource “striped-backgrounds” functional
- New resource “striped-backgrounds (ja)” functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +2
- Schema quality: fail → pass ▲ functional
- 29 Oct 26 −1
- Schema quality: pass → fail ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Oct 26 0
- Schema quality: 32596 → 37957 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New resource “abbreviations” functional
- New resource “abbreviations (ja)” functional
- New resource “background-audio” functional
- New resource “background-audio (ja)” functional
- New resource “background-video” functional
- New resource “background-video (ja)” functional
- New resource “card-link-buttons” functional
- New resource “card-link-buttons (ja)” functional
- New resource “checkout-timers” functional
- New resource “checkout-timers (ja)” functional
- New resource “dark-theme-contrast” functional
- New resource “dark-theme-contrast (ja)” functional
- New resource “descriptive-transcripts” functional
- New resource “descriptive-transcripts (ja)” functional
- New resource “duplicate-ids” functional
- New resource “duplicate-ids (ja)” functional
- New resource “extended-audio-description” functional
- New resource “extended-audio-description (ja)” functional
- New resource “furigana-fields (ja)” functional
- New resource “input-masks” functional
- New resource “input-masks (ja)” functional
- New resource “jargon” functional
- New resource “jargon (ja)” functional
- New resource “kanji-readings (ja)” functional
- New resource “live-audio” functional
- New resource “live-audio (ja)” functional
- New resource “menu-link-toggle” functional
- New resource “menu-link-toggle (ja)” functional
- New resource “picture-sign-in” functional
- New resource “picture-sign-in (ja)” functional
- New resource “qr-codes” functional
- New resource “qr-codes (ja)” functional
- New resource “reading-level” functional
- New resource “reading-level (ja)” functional
- New resource “region-purpose” functional
- New resource “region-purpose (ja)” functional
- New resource “seat-maps” functional
- New resource “seat-maps (ja)” functional
- New resource “section-headings” functional
- New resource “section-headings (ja)” functional
- New resource “session-expiry” functional
- New resource “session-expiry (ja)” functional
- New resource “sign-language” functional
- New resource “sign-language (ja)” functional
- New resource “site-location” functional
- New resource “site-location (ja)” functional
- New resource “skeleton-screens” functional
- New resource “skeleton-screens (ja)” functional
- New resource “spaced-out-words (ja)” functional
- New resource “split-fields” functional
- New resource “split-fields (ja)” functional
- New resource “target-size-enhanced” functional
- New resource “target-size-enhanced (ja)” functional
- New resource “text-blocks” functional
- New resource “text-blocks (ja)” functional
- New resource “timed-pop-ups” functional
- New resource “timed-pop-ups (ja)” functional
- New resource “touch-detection” functional
- New resource “touch-detection (ja)” functional
- 27 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Probed https://easeweb.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easeweb.dev | CN=WE1,O=Google Trust Services,C=US | 5 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 9ea7f8710ca8c9250e5a7b772aa95dda |
| SANs: easeweb.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of easeweb.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| easeweb.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://easeweb.dev/mcp | Verified | 200 | |
| http (plaintext) | http://easeweb.dev/mcp | HTTPS enforced | 301 | https://easeweb.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
before_building ~288
Call BEFORE designing or building any interactive component or screen: menus, dialogs, carousels, tabs, forms, drag and drop, custom controls, cards, tables, charts, animation. This includes wireframes, mockups and prototypes. 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 the 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 returns a version that keeps what the user wanted and passes, plus one sentence to say to the user. Do not refuse such a request, and do not build the failing version quietly.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Guides to return at most (default 6, max 12) |
| locale | string | – | Language of the answer and the guides: en (default) or ja. Japanese answers cite JIS X 8341-3:2016. |
| request | string | yes | What the user asked for, in their words, e.g. "autoplaying hero carousel", "custom dropdown with search", "カード全体をクリックできる一覧" |
No output schema declared.
No examples provided.
check_palette ~264
Call when choosing or changing colours, a palette or design tokens, before they are used 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.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | – | Conformance level to check against (default AA) |
| locale | string | – | Language of the answer and the guides: en (default) or ja. Japanese answers cite JIS X 8341-3:2016. |
| pairs | array | – | Colour pairs to check |
| tokens | object | – | Or named tokens { "ink": "#1b1b1b", "paper": "#fff" }, up to 12; every combination is checked as text |
No output schema declared.
No examples provided.
find_fix ~218
Search 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, EN 301 549, Section 508 and JIS X 8341-3 terms. Topics with no guide yet come back as "in progress". Use it when a finding, a complaint, a failing check or a question names a problem.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Topics to return at most (default 8, max 20) |
| locale | string | – | Language of the answer and the guides: en (default) or ja. Japanese answers cite JIS X 8341-3:2016. |
| query | string | yes | Words, a tag, an ARIA attribute or a WCAG number |
No output schema declared.
No examples provided.
get_guide ~148
The full guide as Markdown, the same 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). Get the slug from find_fix or before_building.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the answer and the guides: en (default) or ja. Japanese answers cite JIS X 8341-3:2016. |
| slug | string | yes | The guide slug, e.g. "native-buttons" |
No output schema declared.
No examples provided.
test_steps ~177
Call AFTER building or fixing something, and before telling the user it is done. For a guide (by slug) or a component (by query) returns the pass criteria, the checks the 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. Hand the person’s checks to the user as written; never report them as done.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the answer and the guides: en (default) or ja. Japanese answers cite JIS X 8341-3:2016. |
| query | string | – | Or a component or problem in words, when the slug is unknown |
| slug | string | – | A guide slug from find_fix or before_building |
No output schema declared.
No examples provided.
How do I install the EaseWeb accessibility MCP server?
EaseWeb accessibility is a hosted endpoint at https://easeweb.dev/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.
remote · easeweb.dev
claude mcp add --transport http dev-easeweb-easeweb 'https://easeweb.dev/mcp'
What is the EaseWeb accessibility MCP server?
EaseWeb accessibility is an MCP server listed in the public MCP registry as dev.easeweb/easeweb. Accessibility guides for coding agents: fixes with working code, test steps, contrast checks. EN/JA. This page covers its hosted endpoint (https://easeweb.dev/mcp).
Is the EaseWeb accessibility MCP server safe to use?
EaseWeb accessibility scores 79 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 EaseWeb accessibility MCP server expose?
EaseWeb accessibility exposes 5 tools: before_building, find_fix, get_guide, test_steps, check_palette. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.
Does the EaseWeb accessibility MCP server require authentication?
No. We connected to EaseWeb accessibility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EaseWeb accessibility MCP server still maintained?
EaseWeb accessibility is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EaseWeb accessibility MCP server?
VerifyMCP ran 13 checks on EaseWeb accessibility, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.