SquatScan

io.github.haseeb-xdPublished by GitHub account haseeb-xdv0.1.0Updated Nov 17, 2026

Detects slopsquatted/typosquatted npm packages before you install them.

The publisher's own server: scan.mx Email Diagnostics

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Checks npm package names for slopsquatting and typosquatting risk, scoring each 0–100 with a GREEN, YELLOW or RED verdict before you install.

What you can do
  • Check a single npm package, optionally at a specific version
  • Check a list of package names in one call
  • Parse an npm install command and check every package it names
  • Explain the risk score with a list of reasons behind each verdict
When to use it
Useful when an AI assistant suggests npm packages and you want to confirm they are real and not attacker-registered lookalikes before running npm install. Also handy for reviewing a whole install command or dependency list in one pass.
Requirements
Runs locally over stdio. Docker installed and running is the documented default (the -i flag is required); alternatively Java 17+ with a built jar. No accounts, API keys or environment variables. Needs network access to the public npm registry.
Before you install
Read-only lookups: it does not install anything, and the assistant still decides when to call it, so it can be skipped unless you instruct it to check every time. Package names are sent to the public npm registry. Verdicts are heuristic risk scores, not guarantees.

Installation

In SourceWeft

  1. Open SquatScan in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SquatScan

SquatScan is an MCP server that checks npm packages for signs of slopsquatting before you install them.

https://github.com/user-attachments/assets/bac28180-2958-4d56-9410-46e5d1373f4c

AI coding assistants sometimes suggest npm packages that don't exist. Attackers register those made-up names and fill them with malware, so the suggested npm install succeeds and installs the attacker's code. SquatScan catches these packages before they are installed.

How it works

For each package name, SquatScan looks it up on the npm registry and combines these signals into a risk score from 0 to 100:

  • whether the package exists at all
  • how close the name is to a popular package (e.g. lodahs vs lodash)
  • how new the package is
  • how many downloads it has
  • whether it links to a source repository
  • how many versions and maintainers it has

The score maps to a verdict:

VerdictScoreWhat to do
🟢 GREENunder 40No strong risk signals. Go ahead.
🟡 YELLOW40–69Some suspicious signals. Check the name before installing.
🔴 RED70 or moreLooks like a squatted package. Don't install it.

Every result includes a reasons list that explains which signals affected the score.

Install

You need Docker installed and running.

Claude Code:

bash
claude mcp add -s user squatscan -- docker run -i --rm ghcr.io/haseeb-xd/squatscan:0.1.0

Claude Desktop (or any MCP client): add this to your config file (Settings → Developer → Edit Config), then fully restart the app:

json
{  "mcpServers": {    "squatscan": {      "command": "docker",      "args": ["run", "-i", "--rm", "ghcr.io/haseeb-xd/squatscan:0.1.0"]    }  }}

The -i flag is required. Without it, Docker closes stdin and the server exits immediately.

SquatScan is also listed in the MCP Registry as io.github.haseeb-xd/squatscan.

Run without Docker (Java 17+)
bash
./mvnw clean package -DskipTestsmkdir -p ~/.squatscan && cp target/squatscan-0.1.0.jar ~/.squatscan/squatscan.jarclaude mcp add -s user squatscan -- java -jar "$HOME/.squatscan/squatscan.jar"

On Windows, use an absolute path with forward slashes, e.g. C:/Users/<you>/.squatscan/squatscan.jar.

Usage

Start a new Claude session, then ask things like:

  • Is lodahs safe to install?
  • Check react, reqeusts and some-hallucinated-pkg-xyz
  • I'm about to run npm install express lodahs. Is that OK?

Tools

ToolWhat it does
check_package(name, version?)Checks one package
check_packages(names[])Checks several packages at once
check_install_command(command)Reads a command like npm install a b c and checks every package in it

Make Claude check every time (recommended)

Claude decides for itself when to call an MCP tool, and it often skips SquatScan. To make it check every time, add this to ~/.claude/CLAUDE.md:

markdown
Before recommending or installing ANY npm package, check every package name with thesquatscan MCP tools. RED: don't install it and suggest the intended package.YELLOW: warn me and ask before continuing. GREEN: go ahead.

Troubleshooting

  • Shows "failed" in /mcp: make sure Docker is running (or that java is on your PATH if you're not using Docker). Run claude --debug to see startup errors.
  • New tools don't appear: start a new Claude session. Sessions that are already running don't pick up newly added servers.

Scope

npm packages only. Runs entirely on your machine; the only network calls go to the public npm registry. No accounts or data collection.

Source: README.md at commit 5cab2a5

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v0.1.0LatestNov 17, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Scan integrations