mcpbeat Sign in

EaseWeb accessibility MCP Server

answering

EaseWeb accessibility is answering right now. Last checked 1 min ago.

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

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
135 ms
Response time
average over 24h
authentication required
Access
streamable-http

Nothing serious here today

Today is the operative word: we check EaseWeb accessibility every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add easeweb --transport http https://easeweb.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://easeweb.dev/mcp
~/.codex/config.toml
[mcp_servers.easeweb]
url = "https://easeweb.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "easeweb": {
      "url": "https://easeweb.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "easeweb": {
      "type": "http",
      "url": "https://easeweb.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URLTransportStateLatencyChecked
https://easeweb.dev/mcp streamable-http needs auth 180 ms 1 min ago

Alternatives to EaseWeb accessibility

same job, measured the same way
Wcag Accessibility
by aditya-ariosity

A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.

60 installs/wk local only
Agentic SDLC MCP
by sakuracianna

Agentic SDLC governance and security controls for AI coding agents working with GitHub.

77 installs/wk local only
Evolize
by evolize

Accessibility scans with evidence, public reports, and fresh checks after fixes.

3 tools answering
SkillFM Claude Code Token Usage
by ericm1018

Claude Code token usage, cost visibility, and SkillFM Beacon AI health checks for MCP agents.

43 installs/wk local only
ProvenPin
by provenpin

Tested, version-pinned code recipes for AI coding agents, each with its last-passed receipt.

3 tools answering
AGENTS.md Generator
by nushey

Analyzes codebases with tree-sitter and generates AGENTS.md files for AI coding agents.

266 installs/wk local only
Token Context MCP
by mck564

On-demand, local code-context MCP server for AI coding agents with Tree-sitter AST.

585 installs/wk local only
ColorPickr
by colorpickr

Contrast checks with fixes, OKLCH harmonies, palettes, color-blind previews and code export.

6 tools answering

EaseWeb accessibility — questions

Answers built from our own checks of this server.

Why is there no tool list for EaseWeb accessibility?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is EaseWeb accessibility working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 135 ms. The bar chart above shows every period we have measured.
How do I connect EaseWeb accessibility?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.
Does EaseWeb accessibility need an API key?
Yes. Every time we knock, EaseWeb accessibility answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is EaseWeb accessibility?
It answers our handshake in 135 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.