MCP Security Server
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 |
|---|---|
| count_lines_in_fileB | Count the number of lines in a text file and return file metadata |
| write_to_fileB | Write content to a file with optional append mode |
| read_file_contentC | Read the content of a file with optional encoding |
| check_outdated_packagesA | Check for outdated npm packages and show current vs latest versions |
| analyze_package_securityB | Run npm security audit to find vulnerabilities in dependencies |
| check_npm_versionB | Check npm version and basic installation info |
| check_npmrc_configC | Check local and global .npmrc configuration files |
| check_npm_global_configC | Check global npm configuration settings |
| verify_registry_configC | Verify npm registry configuration and accessibility |
| check_npm_cacheA | Check npm cache location and verify cache integrity |
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 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.