Skip to main content
Glama
code-alchemist01

Development Tools MCP Server

check_vulnerabilities

Identify security vulnerabilities in project dependencies to enhance code safety and prevent potential exploits.

Instructions

Check for security vulnerabilities in dependencies

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathNoPath to project root

Implementation Reference

  • Handler for the 'check_vulnerabilities' tool. Calls DependencyAnalyzer.analyzeDependencies with vulnerability check enabled and returns summarized vulnerability report.
    case 'check_vulnerabilities': {
      const report = await analyzer.analyzeDependencies(projectPath, {
        checkUnused: false,
        checkOutdated: false,
        checkVulnerabilities: true,
      });
      return {
        vulnerabilities: report.vulnerabilities,
        total: report.vulnerabilities.length,
        critical: report.vulnerabilities.filter((v) => v.severity === 'critical').length,
        high: report.vulnerabilities.filter((v) => v.severity === 'high').length,
      };
    }
  • Input schema and metadata definition for the 'check_vulnerabilities' tool.
    {
      name: 'check_vulnerabilities',
      description: 'Check for security vulnerabilities in dependencies',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description: 'Path to project root',
          },
        },
      },
    },
  • src/server.ts:66-67 (registration)
    MCP server registration and routing logic that matches the tool name against dependencyAnalysisTools (including 'check_vulnerabilities') and dispatches to the handler.
    } else if (dependencyAnalysisTools.some((t) => t.name === name)) {
      result = await handleDependencyAnalysisTool(name, args || {});
  • Core helper method findVulnerabilities that performs the vulnerability scan (currently stubbed, comments indicate npm audit usage). Called when checkVulnerabilities option is true.
    private async findVulnerabilities(_projectPath: string): Promise<Vulnerability[]> {
      // This is a simplified version. In production, we'd use npm audit
      // For now, return empty array - actual implementation would require npm audit API
      try {
        // Would use: const { execSync } = require('child_process');
        // const auditResult = JSON.parse(execSync('npm audit --json', { cwd: projectPath }).toString());
        // return parseAuditResults(auditResult);
        return [];
      } catch {
        return [];
      }
    }
  • TypeScript interface defining the structure of Vulnerability objects returned by the tool.
    export interface Vulnerability {
      name: string;
      severity: 'low' | 'moderate' | 'high' | 'critical';
      title: string;
      url: string;
      dependencyOf?: string;
      fixAvailable?: boolean;
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose critical details like whether it's read-only, requires authentication, has rate limits, returns structured data, or handles errors, leaving significant gaps for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without fluff. It's appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of security vulnerability checking, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'check' entails, what the output looks like, or behavioral traits, making it inadequate for an agent to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the 'projectPath' parameter. The description adds no additional meaning about parameters, such as format examples or constraints, but meets the baseline since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Check for') and target ('security vulnerabilities in dependencies'), which is specific and understandable. However, it doesn't differentiate from sibling tools like 'scan_security_issues' or 'check_outdated_packages', leaving some ambiguity about scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'scan_security_issues' or 'check_outdated_packages'. The description lacks context about prerequisites, timing, or exclusions, offering minimal help for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/code-alchemist01/development-tools-mcp-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server