io.github.vpatser1/mcp-server-security-scanner
NPM · MCP-SERVER-SECURITY-SCANNER · SCANNED SEP 24
Scan MCP configs for 30+ CVEs, prompt injection, tool poisoning; validate OAuth configs
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 50 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 483 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.vpatser1/mcp-server-security-scanner server?
io.github.vpatser1/mcp-server-security-scanner runs locally as an npm package, launched with npx -y mcp-server-security-scanner. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-security-scanner
claude mcp add vpatser1-mcp-server-security-scanner -- npx -y mcp-server-security-scanner
{
"mcpServers": {
"vpatser1-mcp-server-security-scanner": {
"command": "npx",
"args": [
"-y",
"mcp-server-security-scanner"
]
}
}
} {
"servers": {
"vpatser1-mcp-server-security-scanner": {
"command": "npx",
"args": [
"-y",
"mcp-server-security-scanner"
]
}
}
} codex mcp add vpatser1-mcp-server-security-scanner -- npx -y mcp-server-security-scanner
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vpatser1-mcp-server-security-scanner": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-server-security-scanner"
],
"enabled": true
}
}
} openclaw mcp add vpatser1-mcp-server-security-scanner --command npx --arg -y --arg mcp-server-security-scanner
mcp_servers:
vpatser1-mcp-server-security-scanner:
command: "npx"
args: ["-y", "mcp-server-security-scanner"] {
"McpServers": {
"vpatser1-mcp-server-security-scanner": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-server-security-scanner"
]
}
}
} assistant mcp add vpatser1-mcp-server-security-scanner -t stdio -c npx -a -y mcp-server-security-scanner
{
"mcpServers": {
"vpatser1-mcp-server-security-scanner": {
"command": "npx",
"args": [
"-y",
"mcp-server-security-scanner"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/mcp-server-security-scanner@1.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_cves Check Known CVEs ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listAll | boolean | – | If true, returns the full CVE database instead of checking specific servers |
| servers | array | yes | List of MCP servers to check for known CVEs |
No output schema declared.
No examples provided.
generate_report Generate Security Report ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
scan_config Scan MCP Configuration ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Absolute or relative path to the MCP configuration file to scan (e.g. ~/.claude/claude_desktop_config.json) |
No output schema declared.
No examples provided.
scan_tool_definitions Scan Tool Definitions ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tools | array | yes | Array of tool definition objects to scan |
No output schema declared.
No examples provided.
validate_auth Validate Authentication Configuration ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authConfig | object | yes | Authentication configuration object to validate. OAuth fields can be nested under 'oauth' or provided at the top level in camelCase or snake_case. |
No output schema declared.
No examples provided.
What is the io.github.vpatser1/mcp-server-security-scanner server?
io.github.vpatser1/mcp-server-security-scanner is listed in the public MCP registry as io.github.vpatser1/mcp-server-security-scanner. Scan MCP configs for 30+ CVEs, prompt injection, tool poisoning; validate OAuth configs. This page covers its npm package (mcp-server-security-scanner).
Is the io.github.vpatser1/mcp-server-security-scanner server safe to use?
io.github.vpatser1/mcp-server-security-scanner scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vpatser1/mcp-server-security-scanner server expose?
io.github.vpatser1/mcp-server-security-scanner exposes 5 tools: scan_config, scan_tool_definitions, check_cves, validate_auth, generate_report. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Is the io.github.vpatser1/mcp-server-security-scanner server still maintained?
io.github.vpatser1/mcp-server-security-scanner is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vpatser1/mcp-server-security-scanner server under?
io.github.vpatser1/mcp-server-security-scanner declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.