# io.github.xu-c0/cybersec-mcp (npm · @xu-c0/cybersec-mcp)

Cybersecurity MCP server: 323 prompts + 7 workflows for red team, blue team, SOC, cloud, OSINT.

- Trust score: 88/100 (high trust)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-11

## Components

- npm · `@xu-c0/cybersec-mcp`: 88/100 (this document), [markdown](https://verifymcp.io/servers/xu-c0-cybersec-mcp/xu-c0-cybersec-mcp.md), [page](https://verifymcp.io/servers/xu-c0-cybersec-mcp/xu-c0-cybersec-mcp)

## Channel facts

- Registry: `npm`
- Package: `@xu-c0/cybersec-mcp`
- Version: `0.1.2`
- 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-11.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to xu-c0/cybersec-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 82 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 430 tokens (~86/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.

## Install

### Claude

```bash
claude mcp add xu-c0-cybersec-mcp -- npx -y @xu-c0/cybersec-mcp
```

### Codex

```bash
codex mcp add xu-c0-cybersec-mcp -- npx -y @xu-c0/cybersec-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xu-c0-cybersec-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@xu-c0/cybersec-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xu-c0-cybersec-mcp --command npx --arg -y --arg @xu-c0/cybersec-mcp
```

### Hermes

```yaml
mcp_servers:
  xu-c0-cybersec-mcp:
    command: "npx"
    args: ["-y", "@xu-c0/cybersec-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "xu-c0-cybersec-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@xu-c0/cybersec-mcp"
      ]
    }
  }
}
```

## 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-11 (score 88, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-07 (score 85, +4)

- [security improvement] Known CVEs: partial → pass
- [functional] Dependency health: partial → 0.85

### 2026-08-06 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-05 (score 80, +1)

- [security improvement] CVE-2026-69207 no longer affects this package
- [security improvement] Known CVEs: fail → partial

### 2026-08-04 (score 79, +3)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail
- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 76, +50)

- [security improvement] Install scripts: unverified → pass
- [security improvement] Provenance: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] The attested source repository moved: xu-c0/cybersec-mcp
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-08-01 (score 26, +5)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass

## MCP tools (5)

### `cybersec_list_categories` (~39 tokens)

List the 8 cybersecurity prompt categories with descriptions and prompt counts. Call this first to see what domains are covered before listing or fetching specific prompts.

### `cybersec_list_prompts` (~120 tokens)

Search and filter the prompt library. Returns prompt summaries (id, title, useWhen, variables) — up to 50 per call. Follow up with cybersec_get_prompt for the full text.

Input parameters:

- `category` (string): Filter by category id (red-team, blue-team, soc-ops, cloud-security, osint, grc, vuln-analysis, ai-security).
- `search` (string): Free-text search across title, useWhen, subcategory, and prompt body.
- `skill` (string): Filter by skill level.

### `cybersec_get_prompt` (~101 tokens)

Get a specific prompt by id, with optional variable substitution. Returns the full prompt text ready to send to an LLM. Variables not provided remain as [PLACEHOLDERS] in the output and are listed under unfilledVariables.

Input parameters:

- `id` (integer, required): Prompt id (1–323 currently).
- `variables` (object): Object mapping variable name (without brackets) to value, e.g. { TARGET_DOMAIN: "example.com" }.

### `cybersec_list_scenarios` (~48 tokens)

List all 7 scenario workflows — multi-step prompt chains for complete engagements (incident response, pentest, cloud audit, etc.). Each scenario takes variables and walks through chained phases.

### `cybersec_get_scenario` (~122 tokens)

Get a complete scenario workflow with every step expanded (phase, description, prompt text). Variables are substituted across all steps. Use this when the user describes a full engagement (incident, audit, hunt) rather than a single task.

Input parameters:

- `id` (string, required): Scenario id (web-app-pentest, incident-response, cloud-audit, bug-bounty-recon, compliance-audit, threat-hunting, ai-security).
- `variables` (object): Object mapping variable name to value. See cybersec_list_scenarios for each scenario's expected variables.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/xu-c0-cybersec-mcp/xu-c0-cybersec-mcp#diagnostics

## Score history

- 2026-08-11: 88
- 2026-08-10: 86
- 2026-08-09: 86
- 2026-08-08: 85
- 2026-08-07: 85
- 2026-08-06: 81
- 2026-08-05: 80
- 2026-08-04: 79
- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 26
- 2026-07-31: 21
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@xu-c0/cybersec-mcp
- Socket report: https://socket.dev/npm/package/@xu-c0/cybersec-mcp
- Repository: https://github.com/xu-c0/cybersec-mcp
- Changelog RSS feed: https://verifymcp.io/servers/xu-c0-cybersec-mcp/xu-c0-cybersec-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xu-c0-cybersec-mcp/xu-c0-cybersec-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xu-c0-cybersec-mcp/xu-c0-cybersec-mcp