io.github.GuardBee/slopsquat-scanner
guardbee-slopsquat-scanner
Checks declared npm/PyPI dependencies against real registries to catch slopsquatting
alive probed 2026-10-16
4tools
747tokens in Claude Opus 5.5
0.4 %of Claude's 200k window
0.3×the median server
377 msto initialize
9 msto list tools
- Run it
- npx -y @guardbee/mcp-slopsquat-scanner@0.1.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- guardbee-slopsquat-scanner 0.1.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 747 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 803. The o200k_base estimate is 420. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/GuardBee/guardbee-mcp
- Registry
- active, updated 2026-10-13 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.78×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| scan_npm | 231 | 130 | 31 % |
| scan_pip | 212 | 119 | 28 % |
| check_package | 157 | 88 | 21 % |
| scan_directory | 148 | 83 | 20 % |
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- io.github.4hmetuyar/slopsquat-scanner npmjs.com
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.