npm-search-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port on which the server will listen when running in HTTP transport mode. HTTP mode is automatically enabled when this variable is set. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_npm_packagesC | Search for npm packages |
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
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'search_npm_packages' follows a clear verb_noun pattern.
One tool is too few for a server named 'npm-search-mcp-server', which suggests a broader npm-related scope. A single search tool feels thin and incomplete for interacting with npm packages beyond basic searches.
The tool surface is severely incomplete for npm package management. It only provides search functionality, lacking essential operations like getting package details, checking versions, or managing dependencies, which are core to the domain.