WebUAT-Forensic MCP Server

by evozim Your server? Claim it

answering

WebUAT-Forensic is answering right now. Last checked 14 min ago.

Forensic accessibility and UI/UX front-end audit tool for web apps.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

91 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add webapp-uat --transport http https://webapp-uat-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "webapp-uat": {
      "url": "https://webapp-uat-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.webapp-uat]
url = "https://webapp-uat-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "webapp-uat": {
      "url": "https://webapp-uat-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "webapp-uat": {
      "url": "https://webapp-uat-mcp.vercel.app/api/mcp"
    }
  }
}

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

Endpoints

URL	Transport	State	Latency	Checked
https://webapp-uat-mcp.vercel.app/api/mcp	sse	needs auth	91 ms	14 min ago

Alternatives to WebUAT-Forensic

same job, measured the same way

Tapsite

by mgriffen

MCP server for web inspection, design system extraction, and accessibility audits

41 installs/wk local only

Wcag Accessibility

by aditya-ariosity

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

62 installs/wk local only

A11Y Toolkit

by kinti

The accessibility layer for AI coding agents: audit, fix, document and watch - WCAG 2.2.

local only

site-spec

by ariaxhan

MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.

40 installs/wk local only

Kilotest

by jrpool

Ensemble testing of web pages for accessibility, usability, and standards conformity

8 tools answering

Siteaudit

by thegridwork

Audit websites for accessibility, performance, SEO, design, and mobile. 47 WCAG checks.

33 installs/wk local only

Overlayqa

by overlayqa

Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.

94 installs/wk local only

PageLens AI

by pagelens-ai

AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.

answering

WebUAT-Forensic — questions

Answers built from our own checks of this server.

Why is there no tool list for WebUAT-Forensic?

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 WebUAT-Forensic working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 91 ms. The bar chart above shows every period we have measured.

How do I connect WebUAT-Forensic?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 WebUAT-Forensic need an API key?

Yes. Every time we knock, WebUAT-Forensic 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 WebUAT-Forensic?

It answers our handshake in 91 ms on average, which is faster than 84% 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.