pkg-booper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub API token for enhanced rate limits | |
| PKG_BOOPER_DEBUG | No | Enable debug logging | false |
| PKG_BOOPER_CONFIG | No | Path to custom config file | |
| PKG_BOOPER_TIMEOUT | No | Request timeout in ms | 10000 |
| PKG_BOOPER_CACHE_DIR | No | Cache directory | ~/.cache/pkg-booper |
| PKG_BOOPER_CACHE_TTL | No | Cache TTL in seconds | 86400 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pkg-booper-boopC | Look up the latest version and dist-tags for an npm package |
| pkg-booper-sniffC | Analyze an npm package for security signals, facts, and indicators |
| pkg-booper-big-sniff-fileC | Batch analyze all dependencies from a package.json file for security signals |
| pkg-booper-big-sniff-listC | Batch analyze a provided list of dependencies for security signals |
| pkg-booper-clear-cacheB | Clear cached npm package data. Optionally filter by package name or cache type (versions, health, popular) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit-dependencies | Analyze all dependencies in a package.json for security signals and outdated versions |
| check-package-safety | Verify a package is safe before installing |
| usage-guide | Learn how to use pkg-booper tools effectively |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
boop (version lookup) and sniff (security analysis) are clearly distinct, and clear-cache is unambiguous. The only overlap is big-sniff-file vs big-sniff-list, which differ solely by input source (package.json vs provided list), though the descriptions do clarify the boundary.
All tools use the same kebab-case, pkg-booper- prefixed pattern, which is highly consistent. However the actionable verbs are playful and non-self-documenting (boop, sniff, big-sniff), so the scheme is predictable but not transparently descriptive.
Five tools are well-scoped for an npm lookup-and-security-inspection server, with no filler. Each tool maps to a distinct capability (version lookup, single analysis, two batch modes, cache management).
The surface covers version lookup, single/batch security analysis, and cache control, forming a coherent lifecycle. Minor gaps exist around per-package detail (license, maintainers, diff/compare) that agents might want but can work around.