
WebUAT Forensic
Run forensic accessibility and UI/UX front-end audits on your web app through MCP before you ship or reopen a release candidate.
Overview
WebUAT-Forensic is an MCP server for the Ship phase that performs forensic accessibility and UI/UX front-end audits on web apps via remote SSE.
What is this MCP server?
- Forensic accessibility and UI/UX front-end audit capability for web applications
- Remote WebUAT-Forensic MCP over SSE (webapp-uat-mcp.vercel.app)
- Agent-driven audits without maintaining a local Playwright skill in-repo
- Optional premium via EIP-3009 payment-signature per server manifest
- Version 1.0.0; complements manual QA and code review skills
- Server version 1.0.0 in server.json
- One documented SSE remote endpoint
- Optional secret header payment-signature for premium
What problem does it solve?
You are about to ship a web UI but lack time to manually hunt accessibility failures and confusing UX patterns across every view.
Who is it for?
Solo SaaS and indie front-end builders running pre-ship UAT on marketing sites, dashboards, and onboarding flows inside Claude Code or Cursor.
Skip if: Native mobile app store review, pure API contract testing, or teams that require certified WCAG legal attestations only from human auditors.
What do I get? / Deliverables
Your agent produces audit-oriented accessibility and UX findings you can fix before release.
- Forensic accessibility and UI/UX audit output via agent session
- Configured WebUAT-Forensic remote MCP (v1.0.0)
Recommended MCP Servers
Journey fit
Forensic UAT-style audits belong in Ship because they validate the built UI against accessibility and UX expectations immediately pre-release. Testing is the canonical subphase: the server is described as a forensic audit tool for web apps, aligned with pre-ship QA rather than distribution or infra monitoring.
How it compares
Forensic web UX and a11y MCP—not a deployment or monitoring server.
Common Questions / FAQ
Who is WebUAT Forensic for?
Solo builders shipping web apps who want MCP-triggered accessibility and UI/UX forensic audits alongside their agent coding workflow.
When should I use WebUAT Forensic?
Use it in Ship testing when a staging or production URL is ready and you need structured front-end audit signal before launch.
How do I add WebUAT Forensic to my agent?
Add https://webapp-uat-mcp.vercel.app/api/mcp as an SSE remote MCP server; include payment-signature if your tier requires EIP-3009 settlement.