← Registry

Security & Testing

lazynext.com

Audits web pages and HTML for WCAG accessibility violations, returning detailed reports and rule listings.

1 endpoint4 known toolsFirst detected October 3, 2026Last detected October 3, 2026

ENDPOINT 1

https://api.lazynext.com/mcp

No auth detected

MCP server metadata

Name
accessibility-checker
Version
1.0.0
Capabilities
tools

Known tools 4

scan_url

Render and audit a live web page for WCAG 2.

Inferred read-only
scan_html

Audit pasted HTML markup for WCAG violations (static rules — no render, no quota).

Inferred read-only
get_report

Fetch a stored scan report by its id (from a prior scan_url/scan_html result).

Inferred read-only
list_rules

List every WCAG criterion the scanner can emit, with level and detection path.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.accessibility-checker]
url = "https://api.lazynext.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "accessibility-checker": {
      "type": "http",
      "url": "https://api.lazynext.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: accessibility-checker
Remote MCP URL: https://api.lazynext.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "accessibility-checker": {
      "url": "https://api.lazynext.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "accessibility-checker": {
      "type": "http",
      "url": "https://api.lazynext.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "accessibility-checker",
  "transport": "streamable-http",
  "url": "https://api.lazynext.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.