Provides tools for managing npm packages, including checking for outdated packages, running security audits, and verifying configuration and registry settings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Security Server Check for outdated npm packages in my project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This is a Model Context Protocol (MCP) server that provides file operations, npm package management, and configuration checking capabilities.
count_lines_in_file - Count lines in a text file and return metadata
write_to_file - Write content to a file with append/overwrite modes
read_file_content - Read file content with encoding options
check_outdated_packages - Check for outdated npm packages
analyze_package_security - Run npm security audit
check_npm_version - Check npm installation and version
check_npmrc_config - Check local and global .npmrc files
check_npm_global_config - Check global npm configuration
verify_registry_config - Verify npm registry configuration
check_npm_cache - Check npm cache information
Related MCP server: MCP Filesystem Server
Clone or create the project
Install dependencies: npm install
Build the project: npm run build
Run the server: npm start or npm run dev
The server communicates via the Model Context Protocol (MCP) over stdio. It can be integrated with MCP-compatible clients.
{
"name": "count_lines_in_file",
"arguments": {
"file_path": "/path/to/file.txt"
}
}{
"name": "check_outdated_packages",
"arguments": {
"include_dev": true
}
}{
"name": "write_to_file",
"arguments": {
"file_path": "/path/to/output.txt",
"content": "Hello, World!",
"mode": "overwrite"
}
}Path traversal protection
File size limits
Input validation
Error handling
Safe npm command execution
npm run dev - Run in development mode with tsx
npm run build - Build TypeScript to JavaScript
npm start - Run the built server
ISC
Run npm security audit to find vulnerabilities in dependencies
Inputs: audit_level, package_path.
Check npm cache location and verify cache integrity
Inputs: verify_cache.
Check global npm configuration settings
Inputs: config_key.
Check local and global .npmrc configuration files
Inputs: config_path, include_global.
Check npm version and basic installation info
Inputs: no named parameters.
Check for outdated npm packages and show current vs latest versions
Inputs: include_dev, package_path.
Count the number of lines in a text file and return file metadata
Inputs: file_path (required).
Read the content of a file with optional encoding
Inputs: file_path (required), encoding, max_size.
Verify npm registry configuration and accessibility
Inputs: check_auth, registry_url.
Write content to a file with optional append mode
Inputs: content (required), file_path (required), mode, encoding.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Most npm tools are distinguishable by target (audit, cache, registry, outdated, version), but check_npmrc_config and check_npm_global_config clearly overlap, and the three generic file tools don't fit the security theme. An agent could easily pick the wrong config-checking tool.
All tool names follow a consistent verb_noun snake_case pattern (check_*, verify_*, analyze_*, read_*, write_*, count_*). Minor semantic overlap aside, the naming convention is predictable and readable.
Ten tools is a reasonable count and not padded to excess. However, count_lines_in_file, write_to_file, and read_file_content appear unrelated to the security purpose, so not every tool clearly earns its place.
The core npm security surface is decently covered: audit, outdated packages, config, registry, cache, and version. But there are no remediation or deeper analysis actions such as npm audit fix, vulnerability details, or dependency graph inspection, and the file tools don't fill that gap.
Read and write shared BitsWeave context, projects, tasks, and work sessions through MCP.
Manage Nife.io cloud apps, sites, secrets and Git integrations from MCP clients.
A MCP server built for developers enabling Git based project management with project and personal…
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.