io.github.4hmetuyar/slopsquat-scanner
guardbee-slopsquat-scanner
Checks declared npm/PyPI dependencies against real registries to catch slopsquatting
alive probed 2026-10-19
4tools
≈ 420tokens, estimate
≈ 0.2 %of Claude's 200k window
0.3×the median server
326 msto initialize
9 msto list tools
- Run it
- npx -y @guardbee/mcp-slopsquat-scanner@0.1.1 (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, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/GuardBee/guardbee-mcp
- Registry
- active, updated 2026-09-28 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| scan_npm | 130 | 31 % |
| scan_pip | 119 | 28 % |
| check_package | 88 | 21 % |
| scan_directory | 83 | 20 % |
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- io.github.GuardBee/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 Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.