Sniff MCP server
io.github.Aboudjem/sniff·v0.7.1·4 starsQA + a11y scanner: walks your running app's real user flows and reports what's broken.
4 stars
Reviews
Write oneNobody has reviewed Sniff yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Sniff tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 21 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Sniff compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
- GitHub stars
- 4
- more than 82% of 28,688 servers
Install Sniff in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Sniff repository's README, as published. We do not edit it. Read it on GitHub
English · 简体中文 · 日本語 · Español · Français
Point it at your running app. It walks your real user flows in a real browser and tells you what is actually broken, with proof.
What it does · Install · Use it · What you get · Works in your editor · Good to know
claude plugin marketplace add Aboudjem/10x
claude plugin install sniff@10xWhat it does
Most linters read your source without ever running your app, and end-to-end frameworks ask you to write and maintain the tests yourself. sniff opens your running app in a real browser, clicks and fills things like a user would, and judges what actually happened.
submit buttons, forms wiped by the back button, stuck spinners, and mobile overflow.
- It finds 12 classes of bugs, from HTTP 500 routes and dead links to placeholder data, dead
plus the screenshot and the console or network excerpt the check captured. No steps, no finding.
- It proves every one. Every finding carries the route and the ordered steps that produced it,
clean control page, sniff finds 21 of 21 and reports nothing on the control page.
- It has been measured. On a fixture app planted with 21 bugs across all 12 classes, plus a
Install
The block above is the Claude Code path, through the 10x marketplace. For any other agent, the Vercel skills CLI installs the same three skills:
npx skills add Aboudjem/sniffTo use it as a plain command line tool, with no editor involved:
npx sniff-qa --url http://localhost:3000The npm package is sniff-qa and the binary it installs is sniff. Do not run npx sniff, which is an unrelated package.
Node version, project install, and CI
Node.js 22 or newer. npm install -D sniff-qa adds it to a project's devDependencies, and npx sniff-qa ci writes a GitHub Actions workflow with browser caching and report artifacts.
Use it
1. Start your app, with whatever dev server your project already uses.
npm run dev2. Walk it, from a second terminal. sniff auto-detects a dev server on the common ports, so --url is optional, but passing it takes the guesswork out.
npx sniff-qa --url http://localhost:3000Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Sniff: common questions
- Is Sniff MCP server safe?
- Mostly: it is graded B (70/100). Read the Sniff safety report
- Does Sniff need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Sniff maintained?
- The last commit was 59 days ago (2026-09-06). The latest release is v0.7.1.
- How does Sniff compare with other MCP servers?
- safety score 70/100 (higher than 35% of 48,255 servers); github stars 4 (more than 82% of 28,688 servers). Full comparison.