
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
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.
Installation
In SourceWeft
- Open SquatScan in the dashboard and add it to a workspace.
- 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.
lodahsvslodash) - 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:
Every result includes a reasons list that explains which signals affected the score.
Install
You need Docker installed and running.
Claude Code:
Claude Desktop (or any MCP client): add this to your config file (Settings → Developer → Edit Config), then fully restart the app:
The
-iflag 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+)
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-xyzI'm about to run npm install express lodahs. Is that OK?
Tools
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:
Troubleshooting
- Shows "failed" in
/mcp: make sure Docker is running (or thatjavais on your PATH if you're not using Docker). Runclaude --debugto 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
0Version history
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
scan.mx Email Diagnostics
mx.scanOfficial publisher
Remote MCP server that lets an assistant run graded email deliverability and DNS checks on a domain, covering MX, SPF, DKIM, DMARC, blacklists and more.

草料二维码 · 扫码端 (CaoLiao QR Code Scan-side)
im.cli
Read-only remote MCP that lets an assistant look up the public content, history and fillable forms behind a CaoLiao (cli.im) QR code.
InfraScan Cloud
Published by GitHub account SolDevelo
Read-only MCP access to InfraScan Cloud scan results: AWS and repository security, reliability and cost findings with grades, savings and fixes.

Link rot scan and notarized archive — Atom
org.aimlds
Remote Conduit Atoms service that lets an assistant run a link rot scan and produce a notarized archive of the results, per API call.

ASOScan
Published by GitHub account ASOScan
ASOScan is a remote MCP server for App Store Optimization of your own iOS and Android apps, accessed with an ASOScan account via OAuth.