Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

sniff

NPM · SNIFF-QA

Find broken pages in your running web app before users do. Each page bug comes with steps and a fix.

Available components

79 Trust /100

Last scanned (23 hours ago)

Scores higher than 63% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Aboudjem/sniff). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1079 tokens (~179/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/sniff-qa@0.9.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Aboudjem/sniff
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Aboudjem/sniff/.github/workflows/release.yml@refs/tags/v0.9.5
Rekor log index 3954336373
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a3e44b3789f95ca9cf6bc55e185a71bf9947aa27e44ae0cec9274dcbc5134a7b56bf20ca981dbcd92ff9196247689542d4c8cb6328c721c2645549e1f

Background: How many MCP packages publish verified provenance →

Dependencies 1 package
Packages resolved 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,079 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
sniff ~398

Find real, reproducible QA bugs in a web app. Pass { mode, rootDir, baseUrl? }. Use mode:"walk" (RECOMMENDED) to drive a real browser, walk the app's user flows, and report broken pages/links, console & network errors, empty/placeholder data, broken forms, state-loss, dead-ends, bad loading/error states, responsive issues and accessibility, each with reproduction proof, severity, confidence, and a fix. mode:"scan" = source-only (no browser). mode:"report" = load last results. (mode:"run"/"discover" are legacy.) Auto-detects a running dev server if baseUrl is omitted. Prefer this over the narrow tools (sniff_scan / sniff_run / sniff_discover / sniff_report).

NameTypeReqDescription
allboolean–walk: include low-confidence findings too (default false)
appTypearray––
baseUrlstring–URL of the running app (walk/run/discover). Optional, auto-detected if omitted.
dryRunboolean––
forceAppTypestring––
formatstring––
headlessboolean––
maxPagesinteger–walk: max pages to crawl (default 25)
maxScenariosinteger––
maxVariantsPerRuninteger––
maxVariantsPerScenariointeger––
mobileboolean–walk: include the mobile (375px) responsive pass (default true)
modestringyeswalk = autonomous flow-walk that finds real bugs (RECOMMENDED for a running app); scan = source only; run/discover = legacy; report = load last results
onlystring––
realismstring––
rootDirstringyesAbsolute path to the project root directory
seedinteger––

No output schema declared.

No examples provided.

sniff_discover ~309

Run autonomous end-to-end discovery: extract the app domain from source, classify the app type, generate scenarios with edge-case variants, drive them through Playwright, and return a compact summary. Requires a running dev server (baseUrl optional, auto-detected if omitted). Writes HTML/JSON reports to sniff-reports/discovery/.

NameTypeReqDescription
appTypearray–Filter classifier guesses to these app types (does NOT bypass classification; use forceAppType for that)
baseUrlstring–URL of the running app. Optional -- sniff auto-detects localhost servers if omitted.
dryRunboolean–Generate scenarios + classify without launching a browser or writing reports. Useful for preview.
forceAppTypestring–Force a single app type, bypassing the classifier entirely. Use when classification returns blank.
headlessboolean–Run browser in headless mode
maxScenariosinteger–Cap total scenarios (default: 50)
maxVariantsPerRuninteger–Cap edge variants per run (default: 40)
maxVariantsPerScenariointeger–Cap edge variants per scenario (default: 3)
onlystring–Filter scenarios by id substring or app type
realismstring–Realism profile (default: robot in CI, casual-user otherwise)
rootDirstringyesAbsolute path to the project root directory
seedinteger–Replay a specific random seed

No output schema declared.

No examples provided.

sniff_install ~124

Download what a browser walk needs, once: the browser engine (Playwright, axe-core, Lighthouse) and the requested browsers (default: chromium). For chromium that is about 440 MB to download, about 730 MB on disk (measured on macOS arm64, varies by platform). Run this when a sniff tool returns `needsSetup: playwright-browsers`, then retry. It takes about a minute on a fast link; pass a progress token to get progress notifications.

NameTypeReqDescription
projectsarray–Browser projects to install. Defaults to ["chromium"].

No output schema declared.

No examples provided.

sniff_report ~58

Get the results from the most recent sniff scan. Returns findings, severities, and fix suggestions.

NameTypeReqDescription
formatstring–Output format: full JSON or text summary
rootDirstringyesAbsolute path to the project root directory

No output schema declared.

No examples provided.

sniff_run ~112

Run a full quality audit: source scan + browser checks (accessibility, visual regression, performance). The URL is optional -- sniff auto-detects running dev servers. If no server is found, runs source scan only. No API key needed.

NameTypeReqDescription
baseUrlstring–URL of the running app. Optional -- sniff auto-detects localhost servers if omitted.
headlessboolean–Run browser in headless mode
rootDirstringyesAbsolute path to the project root directory

No output schema declared.

No examples provided.

sniff_scan ~78

Scan project source code for bugs. Finds debug statements, placeholder text, dead links, broken imports, hardcoded URLs, and API endpoint issues (missing validation, auth, error handling, secrets). Works offline, no browser or API key needed. Just pass the project path.

NameTypeReqDescription
rootDirstringyesAbsolute path to the project root directory

No output schema declared.

No examples provided.

Install

How do I install the sniff MCP server?

sniff runs locally as an npm package, launched with npx -y sniff-qa --mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

npm · sniff-qa

# add to Claude Code
claude mcp add aboudjem-sniff -- npx -y sniff-qa --mcp
Common questions

What is the sniff MCP server?

sniff is an MCP server listed in the public MCP registry as io.github.Aboudjem/sniff. Find broken pages in your running web app before users do. Each page bug comes with steps and a fix. This page covers its npm package (sniff-qa).

Is the sniff MCP server safe to use?

sniff scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the sniff MCP server expose?

sniff exposes 6 tools: sniff, sniff_scan, sniff_run, sniff_discover, sniff_install, sniff_report. Their descriptions and schemas cost roughly 1,079 tokens of context every time the server is loaded.

Is the sniff MCP server still maintained?

sniff is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the sniff MCP server under?

sniff declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the sniff MCP server?

VerifyMCP ran 15 checks on sniff, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about sniff: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.