io.github.4hmetuyar/slopsquat-scanner
NPM · @GUARDBEE/MCP-SLOPSQUAT-SCANNER
Checks declared npm/PyPI dependencies against real registries to catch slopsquatting
Available components
Last scanned (19 hours ago)
Scores higher than 65% of npm servers
Category Security
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 Security98
- 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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 281 tokens (~70/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +6
- Stability: unverified → 0.43 ▲ functional
- 29 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 56
First indexed and scored.
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 16 Oct 2026 · Analysed npm/@guardbee/mcp-slopsquat-scanner@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_package ~42
Check a single package name against the real npm or PyPI registry
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Which registry to check |
| name | string | yes | Package name |
No output schema declared.
No examples provided.
scan_directory ~52
Auto-detect and check both npm and pip manifests (package.json, requirements.txt, pyproject.toml) in a directory against their real registries
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | Path to the project root directory |
No output schema declared.
No examples provided.
scan_npm ~99
Check every dependency declared in a package.json (dependencies, devDependencies, peerDependencies, optionalDependencies) against the real npm registry -- flags any package name that doesn't exist at all (a likely LLM-hallucinated dependency an attacker may have pre-registered, i.e. 'slopsquatting'), and separately notes any that exist but were only first published very recently.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | Path to the directory containing package.json |
No output schema declared.
No examples provided.
scan_pip ~88
Check every dependency declared in requirements.txt or pyproject.toml against the real PyPI registry -- flags any package name that doesn't exist at all (a likely LLM-hallucinated dependency an attacker may have pre-registered), and separately notes any that exist but were only first published very recently.
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | Path to the directory containing requirements.txt or pyproject.toml |
No output schema declared.
No examples provided.
How do I install the io.github.4hmetuyar/slopsquat-scanner MCP server?
io.github.4hmetuyar/slopsquat-scanner runs locally as an npm package, launched with npx -y @guardbee/mcp-slopsquat-scanner. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @guardbee/mcp-slopsquat-scanner
claude mcp add 4hmetuyar-slopsquat-scanner -- npx -y @guardbee/mcp-slopsquat-scanner
What is the io.github.4hmetuyar/slopsquat-scanner MCP server?
io.github.4hmetuyar/slopsquat-scanner is an MCP server listed in the public MCP registry as io.github.4hmetuyar/slopsquat-scanner. Checks declared npm/PyPI dependencies against real registries to catch slopsquatting. This page covers its npm package (@guardbee/mcp-slopsquat-scanner).
Is the io.github.4hmetuyar/slopsquat-scanner MCP server safe to use?
io.github.4hmetuyar/slopsquat-scanner scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. 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 io.github.4hmetuyar/slopsquat-scanner MCP server expose?
io.github.4hmetuyar/slopsquat-scanner exposes 4 tools: scan_npm, scan_pip, check_package, scan_directory. Their descriptions and schemas cost roughly 281 tokens of context every time the server is loaded.
Is the io.github.4hmetuyar/slopsquat-scanner MCP server still maintained?
io.github.4hmetuyar/slopsquat-scanner is still listed as active in the MCP registry. We last reached this channel on 16 October 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 io.github.4hmetuyar/slopsquat-scanner MCP server under?
io.github.4hmetuyar/slopsquat-scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.