Sniff MCP Server

Connect Sniff to Claude, Cursor or any other MCP client and it stops being a tab you switch to. QA + a11y scanner: walks your running app's real user flows and reports what's broken. The sniff mcp server is what makes that connection.

What the server does

Sniff is an autonomous QA scanner. You point it at a running web app and it walks your app's real user flows in a real (headless) browser (clicking buttons, filling forms, following links) and reports what's actually broken.

• A first-party noise filter drops the junk that isn't your bug: favicons, analytics, hot-module-reload chatter, expected auth redirects, engine aborts
• Accessibility findings are backed by axe-core, which is zero-false-positive by design
• Uncertain findings are suppressed by default — (use --all to see them)
• A broken page is reported once, not re-flagged on every link that points to it

Installation

The server ships on npm as sniff-qa, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by Aboudjem; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.