12 tools from the Npm MCP Server, categorised by risk level.
View the Npm policy →analyze_bundle_size Analyze bundle size impact: minified, gzipped sizes, tree-shaking support, recommendations analyze_capabilities Analyze package capabilities: ESM/CJS support, TypeScript, platforms (Node/Browser/Deno), exports, build tools analyze_npx_command Analyze and validate an npx command before execution (security check) 2/5 analyze_quality Evaluate package quality metrics including maintenance, popularity, and sustainability audit_security Check package for known security vulnerabilities and get recommendations check_compatibility Analyze compatibility of a package with existing project dependencies compare_packages Compare multiple packages side-by-side (features, size, popularity, maintenance, TypeScript support) compare_versions Compare different versions of a package and analyze breaking changes find_similar_packages Find similar/alternative packages based on keywords and functionality get_package_details Get detailed information about a specific npm package including versions, dependencies, and repository info search_packages Search npm registry for packages by name or keywords with popularity ranking 2/5 The Npm MCP server exposes 12 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Npm server.
Npm tools are categorised as Read (11), Write (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept