# io.github.vpatser1/mcp-server-security-scanner (npm · mcp-server-security-scanner)

Scan MCP configs for 30+ CVEs, prompt injection, tool poisoning; validate OAuth configs

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-07

## Components

- npm · `mcp-server-security-scanner`: 60/100 (this document), [markdown](https://verifymcp.io/servers/vpatser1-mcp-server-security-scanner/mcp-server-security-scanner.md), [page](https://verifymcp.io/servers/vpatser1-mcp-server-security-scanner/mcp-server-security-scanner)

## Channel facts

- Registry: `npm`
- Package: `mcp-server-security-scanner`
- Version: `1.1.4`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-07.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 483 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add vpatser1-mcp-server-security-scanner -- npx -y mcp-server-security-scanner
```

### Codex

```bash
codex mcp add vpatser1-mcp-server-security-scanner -- npx -y mcp-server-security-scanner
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vpatser1-mcp-server-security-scanner": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-security-scanner"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vpatser1-mcp-server-security-scanner --command npx --arg -y --arg mcp-server-security-scanner
```

### Hermes

```yaml
mcp_servers:
  vpatser1-mcp-server-security-scanner:
    command: "npx"
    args: ["-y", "mcp-server-security-scanner"]
```

### Other

```json
{
  "mcpServers": {
    "vpatser1-mcp-server-security-scanner": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-security-scanner"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 60)

First indexed and scored.

## MCP tools (5)

### `scan_config` (~85 tokens)

Scan MCP Configuration

Scans an MCP configuration file (claude_desktop_config.json, .mcp.json, etc.) for security vulnerabilities including hardcoded secrets, excessive permissions, insecure transports, missing authentication, and known vulnerable server versions.

Input parameters:

- `configPath` (string, required): Absolute or relative path to the MCP configuration file to scan (e.g. ~/.claude/claude_desktop_config.json)

### `scan_tool_definitions` (~58 tokens)

Scan Tool Definitions

Analyzes MCP tool definitions for security vulnerabilities including prompt injection vectors, tool poisoning patterns, overly broad filesystem access, command injection risks, and data exfiltration patterns.

Input parameters:

- `tools` (array, required): Array of tool definition objects to scan

### `check_cves` (~111 tokens)

Check Known CVEs

Checks a list of MCP server names and optional versions against a database of known CVEs in the MCP ecosystem (covering path traversal, SSRF, auth bypass, prompt injection, data exfiltration, command injection, and SQL injection). Returns matching CVEs with severity, CVSS scores, and remediation steps.

Input parameters:

- `listAll` (boolean): If true, returns the full CVE database instead of checking specific servers
- `servers` (array, required): List of MCP servers to check for known CVEs

### `validate_auth` (~89 tokens)

Validate Authentication Configuration

Validates OAuth 2.1, API key, or bearer token authentication configuration for an MCP server. Checks for proper PKCE usage, token storage security, redirect URI validation, token expiration settings, and overall auth best practices.

Input parameters:

- `authConfig` (object, required): Authentication configuration object to validate. OAuth fields can be nested under 'oauth' or provided at the top level in camelCase or snake_case.

### `generate_report` (~140 tokens)

Generate Security Report

Generates a comprehensive security report from scan results. Includes an executive summary with overall risk score (0-100), detailed findings with remediation steps, and a SOC 2 compliance checklist. Output is Markdown-formatted.

Input parameters:

- `authValidation` (object): Results from validate_auth
- `configScan` (object): Results from scan_config
- `cveCheck` (object): Results from check_cves
- `findings` (array): Direct array of findings to report on. Use this as a simple alternative to passing structured scan results. If provided alongside structured results, these findings are merged in.
- `toolScan` (object): Results from scan_tool_definitions

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/vpatser1-mcp-server-security-scanner/mcp-server-security-scanner#diagnostics

## Score history

- 2026-08-07: 60
- 2026-08-06: 60
- 2026-08-05: 60
- 2026-08-04: 60

## Links

- npm package: https://www.npmjs.com/package/mcp-server-security-scanner
- Socket report: https://socket.dev/npm/package/mcp-server-security-scanner
- Website: https://aivp-mcp.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/vpatser1-mcp-server-security-scanner/mcp-server-security-scanner.xml
- Changelog JSON feed: https://verifymcp.io/servers/vpatser1-mcp-server-security-scanner/mcp-server-security-scanner.json
- HTML version of this page: https://verifymcp.io/servers/vpatser1-mcp-server-security-scanner/mcp-server-security-scanner