io.github.Aboudjem/sniff

MCPcommunity
v0.7.1io.github.AboudjemUnknownUpdated 4mo agoGitHub

QA + a11y scanner: walks your running app's real user flows and reports what's broken.

Point it at your running app. It walks your real user flows in a real browser and tells you what's actually broken, with proof. headless browser walk -> findings with proof" src=" width="100%"> 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…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4GitHub stars
4mo agoLast update
Package
Authorio.github.Aboudjem
LicenseUnknown
Version0.7.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface6 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

sniffNo description published

This tool published no description. Forge does not invent one.

sniff_scanNo description published

This tool published no description. Forge does not invent one.

sniff_runNo description published

This tool published no description. Forge does not invent one.

sniff_discoverNo description published

This tool published no description. Forge does not invent one.

sniff_installNo description published

This tool published no description. Forge does not invent one.

sniff_reportNo description published

This tool published no description. Forge does not invent one.

0 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Point it at your running app. It walks your real user flows in a real browser and tells you what's actually broken, with proof. headless browser walk -> findings with proof" src=" width="100%"> 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. It is not a linter and not a static scanner. It opens your pages, interacts with…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.