io.github.xu-c0/cybersec-mcp
NPM · @XU-C0/CYBERSEC-MCP · SCANNED AUG 11
Cybersecurity MCP server: 323 prompts + 7 workflows for red team, blue team, SOC, cloud, OSINT.
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 →
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
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to xu-c0/cybersec-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 82 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 430 tokens (~86/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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @xu-c0/cybersec-mcp
claude mcp add xu-c0-cybersec-mcp -- npx -y @xu-c0/cybersec-mcp
codex mcp add xu-c0-cybersec-mcp -- npx -y @xu-c0/cybersec-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xu-c0-cybersec-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@xu-c0/cybersec-mcp"
],
"enabled": true
}
}
} openclaw mcp add xu-c0-cybersec-mcp --command npx --arg -y --arg @xu-c0/cybersec-mcp
mcp_servers:
xu-c0-cybersec-mcp:
command: "npx"
args: ["-y", "@xu-c0/cybersec-mcp"] {
"mcpServers": {
"xu-c0-cybersec-mcp": {
"command": "npx",
"args": [
"-y",
"@xu-c0/cybersec-mcp"
]
}
}
} 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.
- 11 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 +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.
- 7 Aug 26 +4
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.85 functional
- 6 Aug 26 +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.
- 5 Aug 26 +1
- CVE-2026-69207 no longer affects this package ▲ security
- Known CVEs: fail → partial ▲ security
- 4 Aug 26 +3
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +50
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- 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 security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
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 11 Aug 2026 · Analysed npm/@xu-c0/cybersec-mcp@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | xu-c0/cybersec-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/xu-c0/cybersec-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 1578233087 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:fdec9a325615f9250a64ec8eca2d04bd9ccf420fc8158628d3bb2d8a39a81964e537e7f1e83b228fd1e5ebe9a50f65cb924b5fad6ea4c51440a4bd6a7 |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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.
cybersec_get_prompt ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Prompt id (1–323 currently). |
| variables | object | – | Object mapping variable name (without brackets) to value, e.g. { TARGET_DOMAIN: "example.com" }. |
No output schema declared.
No examples provided.
cybersec_get_scenario ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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. |
No output schema declared.
No examples provided.
cybersec_list_categories ~39
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cybersec_list_prompts ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
cybersec_list_scenarios ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.