npmguard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| install_packageA | Evaluate the risk of an npm package before installing it. Returns a structured verdict (ok/warn/block) with the signals that triggered. Use this BEFORE calling |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is zero possibility of selecting the wrong tool. Its purpose is clearly defined and distinct from any nonexistent alternatives.
The single tool name 'install_package' follows a clean verb_noun pattern. Although the name implies installation rather than evaluation, it is consistent and predictable within this one-tool set.
The server has just one tool, which feels thin for a typical server and borders on the minimum viable scope. While the tool covers a specific need, it does not reach the 3-15 tool range that indicates a well-populated set.
For the stated purpose of evaluating npm package risk, the tool fully covers the single required action. Minor gaps include lack of support for batch evaluation or detailed policy management, but the core lifecycle of 'check before install' is complete.