Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.YashviGupta15/npm-advisor-mcp

NPM · NPM-ADVISOR-MCP · SCANNED SEP 20

MCP server to search, compare, and recommend npm packages by size, popularity, and maintenance.

Available components

+1 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 784 tokens (~71/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.YashviGupta15/npm-advisor-mcp server?

io.github.YashviGupta15/npm-advisor-mcp runs locally as an npm package, launched with npx -y npm-advisor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · npm-advisor-mcp

# add to Claude Code
claude mcp add yashvigupta15-npm-advisor-mcp -- npx -y npm-advisor-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "yashvigupta15-npm-advisor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "npm-advisor-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "yashvigupta15-npm-advisor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "npm-advisor-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add yashvigupta15-npm-advisor-mcp -- npx -y npm-advisor-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yashvigupta15-npm-advisor-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "npm-advisor-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add yashvigupta15-npm-advisor-mcp --command npx --arg -y --arg npm-advisor-mcp
# ~/.hermes/config.yaml
mcp_servers:
  yashvigupta15-npm-advisor-mcp:
    command: "npx"
    args: ["-y", "npm-advisor-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "yashvigupta15-npm-advisor-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "npm-advisor-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add yashvigupta15-npm-advisor-mcp -t stdio -c npx -a -y npm-advisor-mcp
// mcp.json
{
  "mcpServers": {
    "yashvigupta15-npm-advisor-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "npm-advisor-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/npm-advisor-mcp@0.1.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~784 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit_package ~52

Check an npm package for known security vulnerabilities using the npm advisory database. Returns CVE count, severity breakdown, affected version ranges, and patch availability.

NameTypeReqDescription
package_namestringyesThe npm package name to audit

No output schema declared.

No examples provided.

check_deprecation ~60

Check if an npm package is deprecated, unmaintained, or has an official successor. Analyzes npm deprecation flag, last publish date, maintenance scores, and download trends.

NameTypeReqDescription
package_namestringyesThe npm package name to check

No output schema declared.

No examples provided.

check_registry ~56

Diagnostic tool — shows which registry URL and auth credentials the server resolves for a given package name based on ~/.npmrc. Useful for debugging private registry access.

NameTypeReqDescription
package_namestringyesThe npm package name to check registry resolution for

No output schema declared.

No examples provided.

compare_packages ~53

Compare 2–5 npm packages side-by-side on key metrics: bundle size, downloads, TypeScript support, maintenance, dependencies, and last publish date.

NameTypeReqDescription
packagesarrayyesArray of package names to compare

No output schema declared.

No examples provided.

find_alternatives ~73

Find similar or competing npm packages as alternatives to a given package. Useful when migrating away from deprecated or unmaintained packages.

NameTypeReqDescription
limitnumberMax number of alternatives to return (default: 6, max: 10)
package_namestringyesThe npm package to find alternatives for

No output schema declared.

No examples provided.

generate_install_command ~91

Generate ready-to-paste install commands for a package across npm, yarn, pnpm, and bun. Automatically includes peer dependencies and TypeScript @types if needed.

NameTypeReqDescription
devbooleanInstall as a dev dependency (default: false)
include_peer_depsbooleanInclude peer dependencies in the install command (default: true)
package_namestringyesThe npm package name

No output schema declared.

No examples provided.

get_changelog ~73

Fetch the changelog or recent release notes for an npm package from its GitHub repository. Shows version history, release dates, and what changed.

NameTypeReqDescription
limitnumberNumber of recent releases to show (default: 5, max: 10)
package_namestringyesThe npm package name

No output schema declared.

No examples provided.

get_package_details ~61

Get detailed information about a specific npm package including API surface, README excerpt, dependencies, bundle size, scores, and usage examples.

NameTypeReqDescription
package_namestringyesThe npm package name (e.g., "dayjs", "lodash", "zod")

No output schema declared.

No examples provided.

recommend_package ~132

Get a weighted recommendation from a list of npm packages. Scores based on bundle size (25%), popularity (20%), maintenance (20%), TypeScript support (15%), dependency count (10%), and freshness (10%). Optionally specify a max bundle size or use case to adjust weights.

NameTypeReqDescription
max_size_kbnumberOptional max acceptable gzip bundle size in KB
packagesarrayyesArray of package names to evaluate
require_typescriptbooleanIf true, packages without TypeScript types get penalized
use_casestringAdjusts scoring weights for your target environment

No output schema declared.

No examples provided.

resolve_technical_doubt ~57

Answer a specific technical question about an npm package by analyzing its metadata, README, dependencies, and characteristics.

NameTypeReqDescription
package_namestringyesThe npm package name
questionstringyesThe technical question about the package

No output schema declared.

No examples provided.

search_packages ~76

Search npm for packages matching a feature or keyword. Returns top candidates with downloads, bundle size, and quality scores.

NameTypeReqDescription
limitnumberMaximum number of results (default: 8, max: 15)
querystringyesFeature or keyword to search for (e.g., "date manipulation", "PDF generation")

No output schema declared.

No examples provided.

Common questions

What is the io.github.YashviGupta15/npm-advisor-mcp server?

io.github.YashviGupta15/npm-advisor-mcp is listed in the public MCP registry as io.github.YashviGupta15/npm-advisor-mcp. MCP server to search, compare, and recommend npm packages by size, popularity, and maintenance. This page covers its npm package (npm-advisor-mcp).

Is the io.github.YashviGupta15/npm-advisor-mcp server safe to use?

io.github.YashviGupta15/npm-advisor-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.YashviGupta15/npm-advisor-mcp server expose?

io.github.YashviGupta15/npm-advisor-mcp exposes 11 tools: search_packages, compare_packages, get_package_details, recommend_package, resolve_technical_doubt, and 6 more. Their descriptions and schemas cost roughly 784 tokens of context every time the server is loaded.

Is the io.github.YashviGupta15/npm-advisor-mcp server still maintained?

io.github.YashviGupta15/npm-advisor-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.YashviGupta15/npm-advisor-mcp server under?

io.github.YashviGupta15/npm-advisor-mcp declares the ISC licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.